DOCSLIB.ORG

IBM Z/VSE 6.2 Brings Storage, Processing, Security, Recovery, and Data Transfer Enhancements

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IBM Z/VSE 6.2 Brings Storage, Processing, Security, Recovery, and Data Transfer Enhancements IBM United States Software Announcement 221-201, dated May 4, 2021 IBM z/VSE 6.2 brings storage, processing, security, recovery, and data transfer enhancements Table of contents 1 Overview 5 Technical information 2 Key requirements 7 Ordering information 2 Planned availability date 7 Terms and conditions 2 Description 8 Order now 5 Program number Overview IBM(R) z/VSE(R) is an operating system for the IBM Z(R) platform used for traditional batch and online transaction processing applications. The following hardware support is available with z/VSE 6.2: • Exploitation of the latest IBM System Storage technology: – z/VSE 6.2 supports IBM System Storage TS7700 R5.1. • Exploitation of latest IBM z15TM Model T01 and T02 technology: – z/VSE 6.2 provides native support for System Recovery Boost (APAR DY47832). This enables z/VSE to temporarily boost general-purpose central processors (CPs) running at sub-capacity to full capacity in a logical partition (LPAR) during system IPL and shutdown. – z/VSE 6.2 supports the configurable IBM Crypto Express7S (APAR DY47834), which enables data encryption and Secure Sockets Layer (SSL) acceleration. Elliptic Curve Cryptography (ECC) with a Crypto Express7S can result in accelerated data-in-flight encryption. The following support is already available with z/VSE 6.2: • z/VSE supports the IBM Fibre Connection (FICON(R)) Express16S+ and FICON Express16SA, as well as the OSA-Express6S/7S family. • z/VSE supports IBM Fibre Channel Endpoint Security, which provides server authentication and data encryption to protect the integrity and confidentiality of data. z/VSE support for Transport Layer Security (TLS) 1.3: • TLS 1.3 support (APAR DY30239) is based on VSE Crypto Services/OpenSSL 1.1.1d update (APAR DY47825, in March 2020). • VSE/POWER(R) PNET SSL supports all available ciphers, including TLS 1.3 (APAR DY47842). • CICS(R) TS for z/VSE 2.2 supports TLS 1.3 inbound connections (APAR PH28252). • Interactive User Interface (IUI). Various job skeletons (ICCF library 59) have been updated to include TLS 1.3 cipher suites (APAR PH31756). • Updates for z/VSE Connector Workstation components for OpenSSL TLS 1.3 support (APAR PH35841). IBM Data Language/I (DL/I) VSE 1.12.1 support: • DL/I 1.12.1 adds utility improvements for database recovery (APAR PH29950). IBM United States Software Announcement 221-201 IBM is a registered trademark of International Business Machines Corporation 1 VSE/POWER: • PNODE Generation Macro for Networking Support is updated to enable acceleration of data transfer (APAR DY47835). TCP/IP updates: • IBM TCP/IP for z/VSE 2.2 is updated to the 2.2.8 level (APAR PH27676). Key requirements z/VSE 6.2 introduced an Architectural Level Set that requires IBM zEnterprise(R) 196, IBM zEnterprise 114, or later. Planned availability date May 4, 2021 Description With improved ease of use and exploitation of the latest IBM Z and IBM System Storage technology, z/VSE 6.2 can help clients with growing z/VSE workloads, and can enable them to better protect their investments in the z/VSE platform. z/VSE 6.2 offers the following enhancements: • Enhancements using continuous delivery: – z/VSE 6.2 and CICS TS for z/VSE 2.2 have been generally available since December 1, 2017. Additional functionality has been introduced for online transaction processing, security, and connectivity. – Clients can better integrate z/VSE in a heterogeneous environment using web- based business solutions and z/VSE connectors. • Exploitation of the latest IBM System Storage technology: – z/VSE 6.2 supports IBM System Storage TS7700 R5.1. • Exploitation of latest IBM z15 and IBM z15 Model T02 technology: – z/VSE 6.2 provides native support for System Recovery Boost (APAR DY47832). This enables z/VSE to temporarily boost general-purpose CPs running at sub-capacity to full capacity in an LPAR. It delivers improved overall system and application availability by minimizing the downtime that results from system shutdown and restart operations. -- The speed boost lasts up to 60 minutes during system IPL as well as stand- alone dump processing and up to 30 minutes during system shutdown. -- After the speed boost ends, the CPs being used by the LPAR return to the sub-capacity model speed. This increase applies only to the LPAR being boosted; all other LPARs not being boosted run at sub-capacity model speed, and the machine itself remains a sub-capacity machine. • z/VSE 6.2 supports the configurable Crypto Express7S (APAR DY47834), which enables data encryption and SSL acceleration. ECC with a CEX7 card can result in accelerated data-in-flight encryption: – Instead of using the CEX7 cards in toleration mode and treating them as Crypto Express6S coprocessors and accelerators, the CEX7 cards are now identified as Crypto Express7S and reported as such in messages and command output (APAR DY47834). The following support is already available with z/VSE 6.2: IBM United States Software Announcement 221-201 IBM is a registered trademark of International Business Machines Corporation 2 • z/VSE supports the FICON Express16S+ and FICON Express16SA as well as the OSA-Express6S/7S family. • z/VSE supports IBM Fibre Channel Endpoint Security, which provides server authentication and data encryption to protect the integrity and confidentiality of data. The capabilities of z/VSE 6.2 are further extended with enhancements delivered through continuous delivery: z/VSE support for Transport Layer Security (TLS) 1.3 • TLS 1.3 support (APAR DY30239) is based on VSE Crypto Services/OpenSSL 1.1.1d update (APAR DY47825, in March 2020). • VSE/POWER PNET SSL supports all available ciphers, including TLS 1.3 (APAR DY47842). • CICS TS for z/VSE 2.2 supports TLS 1.3 inbound connections (APAR PH28252). • Interactive User Interface (IUI). Various job skeletons (ICCF library 59) have been updated to include TLS 1.3 cipher suites (APAR PH31756). • Updates for z/VSE Connector Workstation components for OpenSSL TLS 1.3 support (APAR PH35841). With this upgrade, OpenSSL on z/VSE provides support for TLS 1.3. OpenSSL is an open source project that provides an SSL and TLS implementation as well as key management utilities. See the OpenSSL website for details. OpenSSL on z/VSE provides a z/OS(R) compatible SSL programming interface, which enables existing z/VSE SSL/TLS applications, such as the z/VSE Connector Server and the LDAP client, to run transparently with OpenSSL. Although OpenSSL provides software-based encryption for supported algorithms and key lengths, the z/VSE implementation transparently uses cryptographic hardware, when available, for improved performance. Clients benefit from IBM Z cryptographic hardware and its acceleration of cryptographic operations. For further information about how to set up SSL/TLS in z/VSE, see the following: • The z/VSE TCPIP Support manual, especially the section "Selecting the TCP/IP and SSL Implementation to use" • The IBM Redbook Enhanced Networking on IBM z/VSE • The LE/VSE C Run-Time Library Reference manual for further details about the LE/C TCP/IP Socket API Multiplexer DL/I VSE 1.12.1 DL/I adds improvements for database recovery (APAR PH29950). To enable correct recovery in all situations in which DL/I message DLZ004I (I/O-error) or DLZ005I (out of space) can occur, extensions to the DL/I Log Print utility and DL/I Data Base Backout utility have been provided: • A parameter has been introduced for the DL/I log print utility (DLZLOGP0) that can stop the printing and copying of log records when a DL/I log record with a defined sequence number is reached. This function might be needed when only log records that had been written up to a defined point should be applied during DL/I database recovery. • During DL/I database recovery, it might not be necessary to back out all databases for a Program Specification Block (PSB), but only one or a subset of them. To provide this function, a new input control statement has been introduced for the DL/I Data Base Backout utility (DLZBACK0). Next to these extensions, a description of the different situations in which message DLZ004I or message DLZ005I can appear together with the appropriate recovery actions has been provided in the DL/I 1.12.1 Release Guide. VSE/POWER IBM United States Software Announcement 221-201 IBM is a registered trademark of International Business Machines Corporation 3 PNODE Generation Macro for Networking Support is updated to enable acceleration of data transfer (APAR DY47835). To accelerate data transfer between PNET TCP/ IP nodes by up to 50 times, the system administrator needs to generate the Network Definition Table (NDT) on each system with the new PNODE macro operand SPEED=HIGH for the local node. The PNODE macro is described in the VSE/POWER Administration and Operation manual. TCP/IP updates IBM TCP/IP for z/VSE 2.2 is updated to the 2.2.8 level (APAR PH27676). z/VSE service z/VSE product and PTF orders from IBM Shopz are available only through the internet and DVD. Recommended Service Levels (RSLs), including January 7, 2021 RSLs, are found on the IBM: z/VSE- Service and support - Preventive web page. z/ VSE V6.2 is the only z/VSE release in service. z/VSE blogs For current z/VSE blogs, see the Jens Remus' Blog, which is hosted on the IBM Community Platform within the IBM Z and LinuxONE Community. z/VSE documentation For z/VSE product information and documentation, see IBM Documentation. The following IBM Redbooks(R) are available for z/VSE: • Introduction to the New Mainframe: IBM z/VSE Basics • Security on IBM z/VSE • Migration to CICS Transaction Server for z/VSE V2 • z/VSE Using DB2(R) on Linux(R) for System z(R) Section 508 of the US Rehabilitation Act IBM z/VSE 6.2 is capable as of May 4, 2021, when used in accordance with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act, provided that any assistive technology used with the product properly interoperates with it.
Load more

Recommended publications
  • Facility/370: Introduction
    File No. S370-20 Order No. GC20-1800=9 IDl\n \/:u+ •• ".1 I\n"n"': ..... ft IDIVI V IIlUQI .Via"'lllIlv Facility/370: Systems Introduction Release 6 PLC 4 This publication introduces VM/370, and is intended for anyone who is interested in VM/370. However, the reader should have a basic understanding of I BM data processing. VM/370 (Virtual Machine Facility/370) is a system control program (SCP) that tailors the resources and capabilities of a single System/370 computer to provide concurrent users their one unique (virtual) machine. VM/370 consists of a Control Program (CP), which manages the real computer, a Conversational Monitor System (CMS), which is a general-purpose conversational time-sharing system that executes in a virtual machine, a Remote Spooling Communications Subsystem (RSCS), which spools files to and from geographically remote locations, and a Interactive Problem Control System (I PCS), which provides problem analysis and management faci I ities. The first section of the publication is an introduction; it describes what VM/370 can do. The second, third, fourth, and fifth sections describe the Control Program, Conversational Monitor System, Remote Spooling Communications Subsystem, and Interactive Problem Control System respectively. The appendixes include information about VM/370 publication-to-audience relationship and VM/370-related publications for CMS users. , This publication is a prerequisite for the VM/370 system library. --...- --- ---.-- ------- ------ --..- --------- -~-y- Page of GC20-1800-9 As Updated Aug 1, 1979 by TNL GN25-0U89 ~b Edition (Karch 1919) This edition (GC20-1800-~ together with Technical Newsletter GN25-0489. dated August 1, 1919, applies to Release 6 PLC 4 (Program Level Change) of IBM Virtual Machine Facility/310 and to all subsequent releases until otherwise indicated in new editions or Technical Newsletters.
    [Show full text]
  • Z/OS ♦ Z Machines Hardware ♦ Numbers and Numeric Terms ♦ the Road to Z/OS ♦ Z/OS.E ♦ Z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services
    Mainframes The Future of Mainframes Is Now ♦ z/Architecture ♦ z/OS ♦ z Machines Hardware ♦ Numbers and Numeric Terms ♦ The Road to z/OS ♦ z/OS.e ♦ z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services by Steve Comstock The Trainer’s Friend, Inc. http://www.trainersfriend.com 800-993-8716 [email protected] Copyright © 2002 by Steven H. Comstock 1 Mainframes z/Architecture z/Architecture ❐ The IBM 64-bit mainframe has been named "z/Architecture" to contrast it to earlier mainframe hardware architectures ♦ S/360 ♦ S/370 ♦ 370-XA ♦ ESA/370 ♦ ESA/390 ❐ Although there is a clear continuity, z/Architecture also brings significant changes... ♦ 64-bit General Purpose Registers - so 64-bit integers and 64-bit addresses ♦ 64-bit Control Registers ♦ 128-bit PSW ♦ Tri-modal addressing (24-bit, 31-bit, 64-bit) ♦ Over 140 new instructions, including instructions to work with ASCII and UNICODE strings Copyright © 2002 by Steven H. Comstock 2 z/Architecture z/OS ❐ Although several operating systems can run on z/Architecture machines, z/OS is the premier, target OS ❐ z/OS is the successor to OS/390 ♦ The last release of OS/390 was V2R10, available 9/2000 ♦ The first release of z/OS was V1R1, available 3/2001 ❐ z/OS can also run on G5/G6 and MP3000 series machines ♦ But only in 31-bit or 24-bit mode ❐ Note these terms: ♦ The Line - the 16MiB address limit of MVS ♦ The Bar - the 2GiB limit of OS/390 ❐ For some perspective, realize that 16EiB is... ♦ 8 billion times 2GiB ♦ 1 trillion times 16MiB ❐ The current release of z/OS is V1R4; V1R5 is scheduled for 1Q2004 Copyright © 2002 by Steven H.
    [Show full text]
  • Managing a VSE Console Under VM from a Remote Location
    BY DAN ASKEW Managing a VSE Console Under VM From a Remote Location hen working remotely, it is sometimes necessary to make changes to the system or talk an W operator through a problem. Using the techniques presented here, you can manage a VSE console under VM. you ever tried to talk an operator through a VSEPROD. You can display the virtual machine name by HAVE problem from a remote site and thought to issuing the following commands. yourself, “If I could only see the console”? As this article will This command redisplays the last 20 lines from partition BG: examine, there are several ways you can do this if you are VSECMD VSEPROD RED 20L,BG running VSE under VM. The first method I will examine allows you to communicate with the VSE con- This command displays the last line from sole in a crude line mode. The other two the console: methods allow you to actually “steal” the VSECMD VSEPROD RED existing console away from the operator. Have you ever tried to This command displays the last 20 METHOD #1 talk an operator through occurrences of EOJ: VSECMD VSEPROD RED 20l,’EOJ’ The first method I tried used a problem from a remote IBM’s VMCF modules supplied by The syntax of these commands is VSE. ICCF Library 59 contains a site and thought to as follows: member named SKVMVSE. The yourself, “If I could only VSECMD (VSE machine name) comments at the beginning of the RED (number of lines (default is member provide you with the installa- see the console”? 1)), (redisplay command) tion instructions.
    [Show full text]
  • Syncsort for Z/VSE Programmer's Guide Release
    All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort for z/VSE proprietary software system. PROVEN performance SyncSort for z/ VSE Programmer's Guide Release 3. 7 SI-0328-G SyncSort is a registered trademark of Syncsort Incorporated 070809 © Syncsort Incorporated, 2009 All rights reserved. This document contains proprietary and confidential material, and is only for use by licensees of the SyncSort proprietary software system. This publication may not be reproduced in whole or in part, in any form, except with written permission from Syncsort Incorporated. SyncSort is a trademark of Syncsort Incorporated. All other company and product names used herein may be the trademarks of their respective companies. Table of Contents Summary of Changes . v Performance Improvements . v Data Utility Features. v Operating System . vi Messages. vi Chapter 1. Introduction . 1.1 An Introduction to SyncSort for z/VSE. 1.1 SyncSort’s Basic Functions . 1.1 SyncSort’s Data Utility and SortWriter Features . 1.2 Join Processing Sequence . 1.5 Sample SortWriter Report. 1.6 SyncSort’s Operational Features. 1.7 Structure of the Programmer’s Guide. 1.7 Related Reading. 1.9 Chapter 2. SyncSort Control Statements . 2.1 Control Statement Summary Chart . 2.3 Data Utility Processing Sequence. 2.17 Maximum Record Length Allowed . 2.23 Control Statement Examples . 2.25 Rules for Control Statements . 2.25 ALTSEQ Control Statement . 2.30 ANALYZE Control Statement. 2.32 DUPKEYS Control Statement . 2.33 Table of Contents i END Control Statement. 2.38 INCLUDE/OMIT Control Statement .
    [Show full text]
  • Installing the Simple Connection Line Driver Under Z/OS, Z/VSE, MSP, Or Z/VM Installing the Simple Connection Line Driver Under Z/OS, Z/VSE, MSP, Or Z/VM
    Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM Installing the Simple Connection Line Driver Under z/OS, z/VSE, MSP, or z/VM This section describes the installation steps for installing Simple Connection Line Driver on a z/OS host systems. Note: The Simple Connection Line Driver is not supported on MSP or VM/GCS systems. Installation Overview Installation Steps Installation Overview To gain an understanding of the entire installation process, Software AG recommends that you read all of the installation steps before you perform the individual steps: Step Description 1 Verify the connectivity between cooperating nodes. This step is necessary only to support the TCP/IP line driver. It is not necessary for the Simple Connection Line Driver. 2 Unload the Entire Net-Work mainline and Entire Net-Work TCP/IP line driver libraries. 3 Outline your Entire Net-Work configuration and obtain all of the data necessary to configure the Entire Net-Work startup parameters. 4 Alter the Entire Net-Work Startup Job 5 Add the TCPX-specific DRIVER and LINK statements. 6 Configure client information. This step is necessary only to support the Simple Connection Line Driver. It is not necessary for the TCP/IP line driver. 7 Ensure that ADARUN has been linked with attribute AMODE(31). This step is necessary only to support the TCP/IP line driver. It is not necessary for the Simple Connection Line Driver. 8 Start Entire Net-Work and perform installation verifications.
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Introduction-To-Mainframes.Pdf
    Mainframe The term ‘MainFrame’ brings to mind a giant room of electronic parts that is a computer, referring to the original CPU cabinet in a computer of the mid-1960’s. Today, Mainframe refers to a class of ultra-reliable large and medium-scale servers designed for carrier-class and enterprise-class systems operations. Mainframes are costly, due to the support of symmetric multiprocessing (SMP) and dozens of central processors existing within in a single system. Mainframes are highly scalable. Through the addition of clusters, high-speed caches and volumes of memory, they connect to terabyte holding data subsystems. Mainframe computer Mainframe is a very large and expensive computer capable of supporting hundreds, or even thousands, of users simultaneously. In the hierarchy that starts with a simple microprocessor at the bottom and moves to supercomputers at the top, mainframes are just below supercomputers. In some ways, mainframes are more powerful than supercomputers because they support more simultaneous programs. But supercomputers can execute a single program faster than a mainframe. The distinction between small mainframes and minicomputers is vague, depending really on how the manufacturer wants to market its machines. Modern mainframe computers have abilities not so much defined by their single task computational speed (usually defined as MIPS — Millions of Instructions Per Second) as by their redundant internal engineering and resulting high reliability and security, extensive input-output facilities, strict backward compatibility with older software, and high utilization rates to support massive throughput. These machines often run for years without interruption, with repairs and hardware upgrades taking place during normal operation.
    [Show full text]
  • Z/VSE 6.2 Technical Update
    2018 VM Workshop: z/VSE 6.2 technical update z/VSE 6.2 technical update 2018 VM Workshop Greensboro, NC June 28 – 30, 2018 http://www.vmworkshop.org/2018.shtml Ingolf Salm - [email protected] IBM Germany Ingolf’s z/VSE blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/vse/ © Copyright IBM Corporation 2018 2018 VM Workshop: z/VSE 6.2 technical update z/VSE Roadmap Continuous delivery z/VSE releases in service 06/22/2018 DL/I 1.12.1 partitioning z/VSE 6.2 12/01/2017 z114 / z196 or higher, zHPF / SIMD support, Tapeless installation SCSI / ECKD, CICS TS for z/VSE 2.2, security and connector enhancements z/VSE 6.1 11/2015, end of service 06/30/2019 z10 or higher, CICS TS For z/VSE 2.1: CICS EXplorer update, Channels & Containers; TCP/IP For z/VSE 2.1, IPv6/VSE 1.2, IBM Z eXploitation z/VSE 5.2 04/2014, end of service 10/31/2018 z9 or higher, IBM Z eXploitation, device support, Tapeless installation, networking / security enhancements Unsupported z/VSE 5.1 11/2011, end of service 06/30/2016 z/VSE releases z9 or higher , 64 bit virtual, IBM Z eXploitation, z/VSE 5.1.1 06/2012: CICS EXplorer, LFP in LPAR, database connector z/VSE 5.1.2 06/2013: TS1140, 64 bit I/O, openSSL, db connector enhancements z/VSE 4.3 11/2010, end of service 10/31/2014 Virtual storage constraint relieF, 4 digit cuus, z/VSE 4.3.1 08/2011 z/VSE 4.2 October 2008, end of service 10/31/2012 More tasks, more memory, EF For z/VSE 1.1, CPU balancing, SCRT on z/VSE z/VSE 4.2.1 07/2009 - PAV, EF For z/VSE 1.2, z/VSE 4.2.2 04/2010 - IPv6/VSE 05/2010 CICS/VSE end of service
    [Show full text]
  • CA EPIC for Z/VSE Installation and System Guide
    CA EPIC™ for z/VSE Installation and System Guide r5.2 This documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [Show full text]
  • Real World Z/VSE to Z/OS Migration Experience from a Z/VSE Bigot
    Honesty | Loyalty | Integrity | Quality z/VSE to z/OS Migration Experience From a z/VSE Bigot’s Perspective Tony Thigpen – Senior System Programmer Agenda . Customer Background . Methods . Source Conversion . JCL Conversion . Utility Conversion . Operations Conversion . Data Conversion . Training . Issues that were discovered sooner or later . Discussion . Wrap Up Customer Background . Manufacturer located in Mississippi and North Carolina . Initial Configuration: o Z9 in MS running 4 z/OS LPARs (mix of 1.4 and 1.7) – 160mips o Z10 is NC running 5 VSE/ESA LPARs (1.5) – 70mips o Multiple AS/400s in different locations . First major changes o Both CPUs and some AS/400s were relocated to PZG facilities in FL . Second major changes o 3 of the VSE LPARs were slowly migrated off-platform o 2 VSE LPAR was merged into 1 VSE LPAR o All but one of the AS/400s located in FL were eliminated o All z/OS LPARs upgraded to 1.12 to allow them to run on a Z10 . Resulting Configuration: o Z9 in FL running 4 z/OS LPARs (all 1.12) – 150mips o Z10 in FL running 1 VSE/ESA LPAR (1.5) – 70mips Customer Background . Customer goal to cut costs o An os for each machine from IBM ($$) o Adabas for each machine ($$$) o Similar Third-party software on both machines ($$$) o Maintenance, floor space, HVAC costs ($$) o Operations (staff) costs ($) . Customer was concerned with older VSE/ESA o Out of Service o CICS/VS – CICS/TS conversion . The decision was to take the money budgeted for upgrading the VSE and use it instead to migrate the one remaining VSE LPAR to z/OS o Unpopular with VSE programmers but there were only 3 left.
    [Show full text]
  • VM/SP Introduction.Pdf
    GC19-6200-1 File No. S370/4300-20 Program Product GC19-6200-1 File No. S370/4300-20 IBM Virtual Machine/ System Product: Program Product Introduction Program Number 5664-167 Release 2 -----~- - i::~~ Second Edition (April 1982) This edition, GC19-6200-1, is a reV1S10n of GC19-6200-0. It applies to the IBft Virtual ~achine/System Product (5664-167) until otherwise indicated in new editions or ~echnical Newsletters. Changes are continually made to the information contained herein; before using this publication in connection with the operaticn of IBft systems, consult the IB~ 2:i2tem/370 and .!!300 f!:~.§§£!§ Bibli.£g~, GC20-0001, for the editions that are applicable and current. For a list of changes, see page iii. Technical changes or additions to the text cr illustrations are indicated by a vertical bar to the left of the change. It is possible that this material may contain reference to, or information about, IB~ products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that lEft intends to announce such IB~ products, programming, or services in your country. Publications are not stocked at the address given below; requests for IB~ publications should be made to your IBft representative or to the IB~ branch office serving your locality. A form for reader's comments is provided at the back of this publication. If the torm has been removed, comments may be addressed to IB~ Corporation, Programming Publications, Department G60, P.O. Box 6, Endicott, New York, U.S.A.
    [Show full text]
  • United States District Court for the District of Columbia
    UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA _________________________________ ) UNITED STATES OF AMERICA, ) ) Plaintiff, ) ) v. ) Civil Action No. 1:99CV01318 ) COMPUTER ASSOCIATES ) JUDGE: Gladys Kessler INTERNATIONAL, INC. and ) PLATINUM TECHNOLOGY ) DECK TYPE: Antitrust INTERNATIONAL, INC., ) ) DATE STAMP: 05/25/99 Defendants. ) _________________________________) COMPLAINT Joel I. Klein Kent R. Brown Assistant Attorney General Kenneth W. Gaul Weeun Wang John M. Nannes Sanford M. Adler Deputy Assistant Jeremy W. Eisenberg Attorney General Richard Koffman Melinda Foster Constance K. Robinson Jeremy Feinstein Director of Operations and Merger Enforcement Attorneys Nancy M. Goodman Antitrust Division Chief, Computers & Finance U.S. Department of Justice Section Computers & Finance Section Suite 9500 N. Scott Sacks 600 E Street, N.W. Assistant Chief, Computers & Washington, D.C. 20530 Finance Section (202) 307-6200 UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA _________________________________ ) UNITED STATES OF AMERICA, ) ) Plaintiff, ) ) v. ) Civil Action No. 1:99CV01318 ) COMPUTER ASSOCIATES ) JUDGE: Gladys Kessler INTERNATIONAL, INC. and ) PLATINUM TECHNOLOGY ) DECK TYPE: Antitrust INTERNATIONAL, INC., ) ) DATE STAMP: 05/25/99 Defendants. ) _________________________________) COMPLAINT The United States of America, acting under the direction of the Attorney General of the United States, brings this civil action to obtain equitable relief against defendants and alleges as follows: 1. The United States brings this antitrust case to enjoin Computer Associates International, Inc. (hereinafter “CA”) from acquiring PLATINUM technology International, inc. (hereinafter “Platinum”). 2. CA is the world’s largest independent vendor of computer software for mainframe computers and a leading producer of mainframe computer systems management software. Platinum is a direct and substantial competitor to CA in a number of mainframe -2- systems management software products.
    [Show full text]