This document provides guidance on migrating to z/OS Version 1 Release 13 from earlier releases. It describes typical migration steps, changes in this release, and actions system programmers should take before and after installation to ensure a smooth migration. Key actions include setting up an IPCS environment to diagnose problems, migrating control files, updating procedures for message changes, reworking user modifications, and reconnecting non-IBM software and subsystems. The document also covers hardware migration considerations for new IBM servers.
This document provides administration guidance for version 5.5.0 of the HSM for Windows client. It covers installation, configuration, defining migration jobs, reconciliation, commands, and troubleshooting. The document contains chapters on installation, the graphical user interface, migration jobs, commands, backup integration, parameters, and problem determination.
This document provides reference information for administrators about commands and options for IBM Tivoli Storage Manager Version 6.1 for Linux. It contains information about issuing commands from the administrative client and server console, entering administrative commands, controlling command processing, and descriptions of administrative commands.
This document provides a summary of changes and installation instructions for Tivoli Storage Manager Version 5.5 backup-archive clients. It includes details on installing clients for AIX, HP-UX, Linux, Solaris and z/OS, as well as configuring options, registering with servers, and getting started with backups and restores. The document contains over 550 pages covering all aspects of installing and using Tivoli Storage Manager backup-archive clients.
This document provides an administrator's reference for IBM Tivoli Storage Manager Version 6.2 for Windows. It contains information on administering the server from the command-line interface, including issuing commands, entering administrative commands, and descriptions of individual administrative commands. The document contains over 1300 pages of documentation.
This document provides installation and user guidance for Data Protection for Oracle Version 5 Release 5. It contains information on installing Data Protection for Oracle on AIX, HP-UX, Linux, and Solaris operating systems. It also provides instructions for configuring Data Protection for Oracle and the Tivoli Storage Manager client, and for using RMAN and the Data Protection for Oracle utilities to back up Oracle databases to Tivoli Storage Manager storage.
This document provides installation and configuration instructions for Data Protection for Oracle Version 5 Release 4. It allows for the backup of Oracle 9i and Oracle 10g databases to Tivoli Storage Manager storage through integration with the RMAN Media Management API. Instructions are provided for AIX, HP-UX, Linux, and Solaris platforms. The document also provides information on configuring Tivoli Storage Manager options, defining policies, using the RMAN and Data Protection for Oracle utilities, and troubleshooting.
This document provides an overview and introduction to installing and migrating to IBM Tivoli Workload Scheduler V8.3. It covers prerequisites, a new installation process using a wizard, upgrading from previous versions, and new features such as an improved infrastructure using WebSphere and DB2/Oracle databases. The document is intended to help users get started with V8.3 and provide best practices for installation and migration.
This document provides a guide for installing and configuring IBM Tivoli Workload Scheduler for z/OS. It covers topics such as installing SMF and JES exits, allocating required data sets, creating started tasks to run the Tracker, Controller and DataStore components, and setting up communication methods. The document is intended for system programmers and administrators responsible for installing and customizing the workload scheduler.
This document provides administration guidance for version 5.5.0 of the HSM for Windows client. It covers installation, configuration, defining migration jobs, reconciliation, commands, and troubleshooting. The document contains chapters on installation, the graphical user interface, migration jobs, commands, backup integration, parameters, and problem determination.
This document provides reference information for administrators about commands and options for IBM Tivoli Storage Manager Version 6.1 for Linux. It contains information about issuing commands from the administrative client and server console, entering administrative commands, controlling command processing, and descriptions of administrative commands.
This document provides a summary of changes and installation instructions for Tivoli Storage Manager Version 5.5 backup-archive clients. It includes details on installing clients for AIX, HP-UX, Linux, Solaris and z/OS, as well as configuring options, registering with servers, and getting started with backups and restores. The document contains over 550 pages covering all aspects of installing and using Tivoli Storage Manager backup-archive clients.
This document provides an administrator's reference for IBM Tivoli Storage Manager Version 6.2 for Windows. It contains information on administering the server from the command-line interface, including issuing commands, entering administrative commands, and descriptions of individual administrative commands. The document contains over 1300 pages of documentation.
This document provides installation and user guidance for Data Protection for Oracle Version 5 Release 5. It contains information on installing Data Protection for Oracle on AIX, HP-UX, Linux, and Solaris operating systems. It also provides instructions for configuring Data Protection for Oracle and the Tivoli Storage Manager client, and for using RMAN and the Data Protection for Oracle utilities to back up Oracle databases to Tivoli Storage Manager storage.
This document provides installation and configuration instructions for Data Protection for Oracle Version 5 Release 4. It allows for the backup of Oracle 9i and Oracle 10g databases to Tivoli Storage Manager storage through integration with the RMAN Media Management API. Instructions are provided for AIX, HP-UX, Linux, and Solaris platforms. The document also provides information on configuring Tivoli Storage Manager options, defining policies, using the RMAN and Data Protection for Oracle utilities, and troubleshooting.
This document provides an overview and introduction to installing and migrating to IBM Tivoli Workload Scheduler V8.3. It covers prerequisites, a new installation process using a wizard, upgrading from previous versions, and new features such as an improved infrastructure using WebSphere and DB2/Oracle databases. The document is intended to help users get started with V8.3 and provide best practices for installation and migration.
This document provides a guide for installing and configuring IBM Tivoli Workload Scheduler for z/OS. It covers topics such as installing SMF and JES exits, allocating required data sets, creating started tasks to run the Tracker, Controller and DataStore components, and setting up communication methods. The document is intended for system programmers and administrators responsible for installing and customizing the workload scheduler.
This document provides guidance for administrators on configuring and using VMware vCenter Site Recovery Manager (SRM). SRM allows administrators to plan, test, and execute disaster recovery of VMs managed by vCenter Server. The document covers topics such as assigning privileges and permissions in SRM, creating protection groups for VMs, developing and testing recovery plans, customizing IP and networking settings during recovery, and troubleshooting SRM operations.
Get answers to the frequently Asked Questions about IBM zEnterprise EC12 (zEC12). For more information on System z, visit http://ibm.co/PNo9Cb.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
Tivoli Workload Scheduler LoadLeveler Installation Guide provides instructions for installing and configuring TWS LoadLeveler on AIX and Linux systems. It includes planning the installation, installing the software, configuring user accounts and directories, and setting environment variables. The guide also covers installing TWS LoadLeveler in a submit-only configuration and migrating from a previous version.
This document provides instructions for installing and configuring IBM Tivoli Storage Manager Version 6.2 for AIX. It contains 10 chapters that cover planning the installation, installing the Tivoli Storage Manager server and client API, configuring the server, installing additional components like the reporting and monitoring feature, upgrading from previous versions, and uninstalling Tivoli Storage Manager. It also includes appendices with information on installation log files and accessibility features.
Learn about IBM Ported Tools for z/OS: OpenSSH User's Guide. This document presents the information you need to set up and use IBM Ported Tools for z/OS: OpenSSH. This document is for system programmers who run a z/OS system with z/OS UNIX System Services (z/OS UNIX), and for their users who use IBM Ported Tools for z/OS: OpenSSH. On other open systems, some system programmer tasks might be done by an administrator. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit http://bit.ly/KWh5Dx to 'Follow' the official Twitter handle of IBM India Smarter Computing.
This document provides an overview and technical details about IBM Tivoli OMEGAMON XE V3.1, a performance monitoring and problem determination tool for z/OS environments. It discusses the product architecture and components, data collection processes, high availability features, installation and configuration procedures, and maintenance tasks. The document is intended for system programmers and administrators responsible for implementing and managing OMEGAMON solutions.
This document provides an overview and instructions for configuring and using Tivoli Workload Scheduler LoadLeveler, including:
- LoadLeveler is a job management and scheduling system that allows sharing compute resources across a network. It defines jobs, machines, and scheduling policies.
- LoadLeveler uses daemons to process jobs through various states from pending to completed. Daemons include the master daemon, Schedd, startd, negotiator, kbdd, and gsmonitor.
- The document provides details on installing and configuring LoadLeveler, including defining administrators, the cluster, machines, job classes, accounting settings, and more. It also describes operating system support and considerations for using
Cisco UCS B200 M3 Blade Server with VMware: Uncompromised virtual desktop per...Principled Technologies
A server that supports greater density of hosted virtual desktops without sacrificing performance will minimize the cost of your infrastructure and improve ROI. In our tests, the Cisco UCS B200 M3 Blade Server running VMware View 5 with VMware vSphere 5 provided impressive virtual desktop hosting density. The Cisco UCS solution delivered 186 concurrent VMware View 5 virtual desktops with acceptable user response times and minimal bandwidth usage.
1) The document discusses client-server architecture for multiplayer online games and the tradeoffs between consistency and responsiveness when synchronizing game states across clients.
2) User studies with games like Quake III Arena and Unreal Tournament found that latency below 100ms had little effect on gameplay but latency over 200ms started to become annoying to players.
3) Different types of games, like real-time strategy games, can tolerate higher latency than first-person shooter games due to differences in required reaction time. Maintaining consistency is more important than maximizing responsiveness depending on the game.
Implements BIOS emulation support for BHyVeTakuya ASADA
This document discusses implementing BIOS emulation support for BHyVe, the hypervisor component of FreeBSD. It provides an overview of BHyVe's internal structure, including how it uses Intel VT-x hardware-assisted virtualization to run guest virtual machines. It then outlines a project to add BIOS emulation capabilities to BHyVe in order to support booting legacy systems within BHyVe virtual machines, as is done in other hypervisors like KVM through the use of emulated BIOS code. Alternatives and challenges to implementing BIOS emulation for BHyVe are also discussed.
This document provides installation and configuration instructions for Data Protection for Oracle, which allows backups of Oracle databases to Tivoli Storage Manager. It describes requirements for supported Windows platforms, outlines the installation process, and provides guidance on configuring Tivoli Storage Manager options and policies. It also covers using Recovery Manager (RMAN) and the provided utilities to perform backups and restores. The document contains appendices with a quick start guide, using the Tivoli scheduler, support information, and accessibility details.
Hardware support for efficient virtualizationLennox Wu
The document discusses hardware support for efficient virtualization. It begins by classifying virtualization techniques as full virtualization, paravirtualization, or hardware-assisted virtualization. It then covers the challenges of software-only virtualization on Intel x86 processors and describes hardware virtualization extensions like Intel VT-x and VT-d, as well as AMD-V. These extensions address issues like ring compression and address space compression. The document also discusses I/O virtualization techniques like Intel VT-c and AMD IOMMU, as well as the performance of different virtualization platforms like KVM, Xen, and VirtualBox on Linux.
This document provides installation and configuration instructions for Tivoli Storage Manager Version 6.1. It contains information on installing components such as the server, client API, server languages, Administration Center, and reporting and monitoring feature. It also provides guidance on capacity planning, configuration, upgrading, and uninstalling Tivoli Storage Manager.
Hardware support for virtualization originated in the 1970s with goals of running multiple virtual machines on a single physical machine. A key requirement was virtualization allowing equivalent execution of programs in a virtual environment as running natively. The x86 architecture posed challenges to virtualization due to sensitive instructions. Intel Virtualization Technology (VT-x) added hardware support for virtualization on x86 by introducing a new CPU operation mode called VMX non-root, and transitions between it and VMX root mode. This reduced the need for software emulation of sensitive instructions and improved virtualization performance.
This document discusses storage allocation and LUN creation on an EMC Symmetrix storage array. It describes using the symconfigure command line tool to create multiple striped meta LUNs from existing hyper LUNs on a Symmetrix array with a serial ID of 1098. The symconfigure operation creates two meta LUNs, one from devices 10E8, 10E9, and 110E, and another from devices 111A, 111B, 111C, 111D, 111E, and 111F, configuring them both in a striped format. It also validates the changes against the Control Center management tool.
This document discusses improvements to PCI pass-through in a virtualized environment. It provides background on why SCSI support is important for reliability. It then summarizes the current status of pvSCSI enhancements, including LUN and host pass-through modes. It also discusses requirements and status for booting a guest using PCI pass-through, such as BIOS support and calling PCI expansion ROMs. Challenges with PXE boot and concerns about I/O addressing are also noted.
This document provides release notes for Intel Turbo Memory version 1.5.0.1013. It describes supported operating systems and hardware, behavioral considerations, feature sets, issues fixed and known issues in this release. The document provides guidance on power policies, resume time measurement, ReadyBoost status, NVCACHE drive initialization, and upgrading or replacing Intel Turbo Memory.
Hypervisors are a kind of software which runs different virtual systems called virtual machines on a single computer giving the view to guest running on each virtual machine that it is running on its own single computer. This presentation talks about hypervisors and different techniques of their implementation in brief.
This document provides an installation guide for IBM Tivoli Storage Manager Version 6.2. It contains instructions for installing Tivoli Storage Manager server and client components, including the reporting and monitoring feature and Administration Center. The guide has chapters on planning installation, installing Tivoli Storage Manager, configuring after installation, upgrading from previous versions, and uninstalling Tivoli Storage Manager. It also includes appendices with log file and service information.
Advanced virtualization techniques for FAUmachinewebhostingguy
This document describes advanced virtualization techniques used in FAUmachine, a virtual PC developed by researchers. It presents a just-in-time compiler that can transform kernel mode code into code suitable for execution in a user mode simulator. This allows system-level binaries and operating systems like Windows to run virtually. It also describes a small host kernel modification to simplify system call redirection, improving virtual machine performance. Details are given on the just-in-time compiler and kernel extension, and their impact on performance is evaluated.
Learn about Networking on z/OS. This part of the z/OS basic skills information center is intended to provide information systems personnel with the background knowledge and skills necessary to begin using the basic communications facilities of a mainframe based system. It provides a broad understanding of networking principles and the hardware and software components necessary to allow the mainframe to participate in a high volume data communications network. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
This document provides guidance for administrators on configuring and using VMware vCenter Site Recovery Manager (SRM). SRM allows administrators to plan, test, and execute disaster recovery of VMs managed by vCenter Server. The document covers topics such as assigning privileges and permissions in SRM, creating protection groups for VMs, developing and testing recovery plans, customizing IP and networking settings during recovery, and troubleshooting SRM operations.
Get answers to the frequently Asked Questions about IBM zEnterprise EC12 (zEC12). For more information on System z, visit http://ibm.co/PNo9Cb.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
Tivoli Workload Scheduler LoadLeveler Installation Guide provides instructions for installing and configuring TWS LoadLeveler on AIX and Linux systems. It includes planning the installation, installing the software, configuring user accounts and directories, and setting environment variables. The guide also covers installing TWS LoadLeveler in a submit-only configuration and migrating from a previous version.
This document provides instructions for installing and configuring IBM Tivoli Storage Manager Version 6.2 for AIX. It contains 10 chapters that cover planning the installation, installing the Tivoli Storage Manager server and client API, configuring the server, installing additional components like the reporting and monitoring feature, upgrading from previous versions, and uninstalling Tivoli Storage Manager. It also includes appendices with information on installation log files and accessibility features.
Learn about IBM Ported Tools for z/OS: OpenSSH User's Guide. This document presents the information you need to set up and use IBM Ported Tools for z/OS: OpenSSH. This document is for system programmers who run a z/OS system with z/OS UNIX System Services (z/OS UNIX), and for their users who use IBM Ported Tools for z/OS: OpenSSH. On other open systems, some system programmer tasks might be done by an administrator. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit http://bit.ly/KWh5Dx to 'Follow' the official Twitter handle of IBM India Smarter Computing.
This document provides an overview and technical details about IBM Tivoli OMEGAMON XE V3.1, a performance monitoring and problem determination tool for z/OS environments. It discusses the product architecture and components, data collection processes, high availability features, installation and configuration procedures, and maintenance tasks. The document is intended for system programmers and administrators responsible for implementing and managing OMEGAMON solutions.
This document provides an overview and instructions for configuring and using Tivoli Workload Scheduler LoadLeveler, including:
- LoadLeveler is a job management and scheduling system that allows sharing compute resources across a network. It defines jobs, machines, and scheduling policies.
- LoadLeveler uses daemons to process jobs through various states from pending to completed. Daemons include the master daemon, Schedd, startd, negotiator, kbdd, and gsmonitor.
- The document provides details on installing and configuring LoadLeveler, including defining administrators, the cluster, machines, job classes, accounting settings, and more. It also describes operating system support and considerations for using
Cisco UCS B200 M3 Blade Server with VMware: Uncompromised virtual desktop per...Principled Technologies
A server that supports greater density of hosted virtual desktops without sacrificing performance will minimize the cost of your infrastructure and improve ROI. In our tests, the Cisco UCS B200 M3 Blade Server running VMware View 5 with VMware vSphere 5 provided impressive virtual desktop hosting density. The Cisco UCS solution delivered 186 concurrent VMware View 5 virtual desktops with acceptable user response times and minimal bandwidth usage.
1) The document discusses client-server architecture for multiplayer online games and the tradeoffs between consistency and responsiveness when synchronizing game states across clients.
2) User studies with games like Quake III Arena and Unreal Tournament found that latency below 100ms had little effect on gameplay but latency over 200ms started to become annoying to players.
3) Different types of games, like real-time strategy games, can tolerate higher latency than first-person shooter games due to differences in required reaction time. Maintaining consistency is more important than maximizing responsiveness depending on the game.
Implements BIOS emulation support for BHyVeTakuya ASADA
This document discusses implementing BIOS emulation support for BHyVe, the hypervisor component of FreeBSD. It provides an overview of BHyVe's internal structure, including how it uses Intel VT-x hardware-assisted virtualization to run guest virtual machines. It then outlines a project to add BIOS emulation capabilities to BHyVe in order to support booting legacy systems within BHyVe virtual machines, as is done in other hypervisors like KVM through the use of emulated BIOS code. Alternatives and challenges to implementing BIOS emulation for BHyVe are also discussed.
This document provides installation and configuration instructions for Data Protection for Oracle, which allows backups of Oracle databases to Tivoli Storage Manager. It describes requirements for supported Windows platforms, outlines the installation process, and provides guidance on configuring Tivoli Storage Manager options and policies. It also covers using Recovery Manager (RMAN) and the provided utilities to perform backups and restores. The document contains appendices with a quick start guide, using the Tivoli scheduler, support information, and accessibility details.
Hardware support for efficient virtualizationLennox Wu
The document discusses hardware support for efficient virtualization. It begins by classifying virtualization techniques as full virtualization, paravirtualization, or hardware-assisted virtualization. It then covers the challenges of software-only virtualization on Intel x86 processors and describes hardware virtualization extensions like Intel VT-x and VT-d, as well as AMD-V. These extensions address issues like ring compression and address space compression. The document also discusses I/O virtualization techniques like Intel VT-c and AMD IOMMU, as well as the performance of different virtualization platforms like KVM, Xen, and VirtualBox on Linux.
This document provides installation and configuration instructions for Tivoli Storage Manager Version 6.1. It contains information on installing components such as the server, client API, server languages, Administration Center, and reporting and monitoring feature. It also provides guidance on capacity planning, configuration, upgrading, and uninstalling Tivoli Storage Manager.
Hardware support for virtualization originated in the 1970s with goals of running multiple virtual machines on a single physical machine. A key requirement was virtualization allowing equivalent execution of programs in a virtual environment as running natively. The x86 architecture posed challenges to virtualization due to sensitive instructions. Intel Virtualization Technology (VT-x) added hardware support for virtualization on x86 by introducing a new CPU operation mode called VMX non-root, and transitions between it and VMX root mode. This reduced the need for software emulation of sensitive instructions and improved virtualization performance.
This document discusses storage allocation and LUN creation on an EMC Symmetrix storage array. It describes using the symconfigure command line tool to create multiple striped meta LUNs from existing hyper LUNs on a Symmetrix array with a serial ID of 1098. The symconfigure operation creates two meta LUNs, one from devices 10E8, 10E9, and 110E, and another from devices 111A, 111B, 111C, 111D, 111E, and 111F, configuring them both in a striped format. It also validates the changes against the Control Center management tool.
This document discusses improvements to PCI pass-through in a virtualized environment. It provides background on why SCSI support is important for reliability. It then summarizes the current status of pvSCSI enhancements, including LUN and host pass-through modes. It also discusses requirements and status for booting a guest using PCI pass-through, such as BIOS support and calling PCI expansion ROMs. Challenges with PXE boot and concerns about I/O addressing are also noted.
This document provides release notes for Intel Turbo Memory version 1.5.0.1013. It describes supported operating systems and hardware, behavioral considerations, feature sets, issues fixed and known issues in this release. The document provides guidance on power policies, resume time measurement, ReadyBoost status, NVCACHE drive initialization, and upgrading or replacing Intel Turbo Memory.
Hypervisors are a kind of software which runs different virtual systems called virtual machines on a single computer giving the view to guest running on each virtual machine that it is running on its own single computer. This presentation talks about hypervisors and different techniques of their implementation in brief.
This document provides an installation guide for IBM Tivoli Storage Manager Version 6.2. It contains instructions for installing Tivoli Storage Manager server and client components, including the reporting and monitoring feature and Administration Center. The guide has chapters on planning installation, installing Tivoli Storage Manager, configuring after installation, upgrading from previous versions, and uninstalling Tivoli Storage Manager. It also includes appendices with log file and service information.
Advanced virtualization techniques for FAUmachinewebhostingguy
This document describes advanced virtualization techniques used in FAUmachine, a virtual PC developed by researchers. It presents a just-in-time compiler that can transform kernel mode code into code suitable for execution in a user mode simulator. This allows system-level binaries and operating systems like Windows to run virtually. It also describes a small host kernel modification to simplify system call redirection, improving virtual machine performance. Details are given on the just-in-time compiler and kernel extension, and their impact on performance is evaluated.
Learn about Networking on z/OS. This part of the z/OS basic skills information center is intended to provide information systems personnel with the background knowledge and skills necessary to begin using the basic communications facilities of a mainframe based system. It provides a broad understanding of networking principles and the hardware and software components necessary to allow the mainframe to participate in a high volume data communications network. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
This presentation provides an overview of some of the concepts and functions associated with z/OS Communications Server's exploitation of the System z sysplex capability. This includes topics such as dynamic VIPA, sysplex distributor, and sysplex autonomics.
z/OS V2R2 Communications Server OverviewzOSCommserver
This presentation provides an overview of features in the upcoming z/OS V2R2 Communications Server. Features to be discussed include:
- Improved scalability with 64-bit support for the TCP/IP stack
- Shared Memory Communications over RDMA (SMC-R) adapter virtualization
- Security improvements such as AT-TLS and FTP support for TLS session reuse
- The ability to configure the TCP/IP stack via the IBM Configuration Assistant for z/OSMF
- Support for CICS transaction tracking
- TCP/IP autonomics enhancements
… and many more features!
TN3270 Access to Mainframe SNA ApplicationszOSCommserver
This presentation presents the basics of the TN3270 protocol, and discusses how to configure the TN3270 server provided with z/OS Communications Server.
This presentation discusses the principles of IP Routing as they apply to z/OS, the z/OS implementation of static routing through the TCP/IP profile, and dynamic routing with OMPROUTE.
The document discusses implementing a Parallel Sysplex which couples multiple z/OS systems together using hardware and software services. Key steps include defining coupling facility structures, configuring XCF signalling paths using CTCs or a coupling facility, formatting and configuring sysplex couple data sets, and defining CFRM policies to manage coupling facility resources.
Communications Server provides TCP/IP and SNA connectivity and services on z/OS. It combines the prior VTAM and TCP/IP products and provides common networking functions. Applications can access networks using SNA APIs, sockets APIs, or standard TCP/IP applications. Communications Server supports both SNA and TCP/IP protocols and their integration.
The document discusses legal and illegal migration. It defines legal migration as migration with formal permission, while illegal migration is defined as entering a country without formal permission, such as illegal aliens or boat people. Some reasons for illegal migration include overpopulation, poverty, trade liberalization, and economics/labor market factors. Effects of illegal migration include rising unemployment, tax reductions, increased crime rates, and threats to traditional culture from different cultures. Proposed solutions include policy changes and repatriation programs.
This document provides guidance for upgrading the IBM Tivoli Storage Manager server from version 5 to version 6.1. It discusses planning the upgrade, including checking prerequisites, preparing space, and backing up data. It then describes four upgrade scenarios: upgrading on the same system using media, upgrading on the same system over the network, upgrading to a new system using media, and upgrading to a new system over the network. Each scenario provides step-by-step instructions for installing upgrade utilities, preparing the existing database, installing the new server software, and upgrading the database using either the upgrade wizard or manual utilities. The document also covers testing the upgrade and reference information to help plan the process.
This document provides guidance for upgrading an IBM Tivoli Storage Manager server from version 5 to version 6.1. It discusses planning the upgrade process, including checking prerequisites, preparing space, backing up data, and installing upgrade utilities. It then covers four upgrade scenarios: upgrading on the same system using media, upgrading on the same system over the network, upgrading to a new system using media, and upgrading to a new system over the network. Each scenario provides step-by-step instructions for upgrading the server database using either an upgrade wizard or manual utilities. The document also includes reference information on command changes and new messages.
This document provides an installation and configuration guide for IBM Tivoli Directory Server version 6.3. It contains information about installing the server, clients, language packs, and other components across various platforms like Windows, Linux, AIX, Solaris, and HP-UX. The guide also describes how to create and administer directory server instances, configure databases, tune performance, back up and restore data, and more.
This document provides an introduction and planning guide for the IBM System Storage DS8800 and DS8700 storage systems. It describes the features and functions of these systems including hardware components, data management features, licensing, and planning considerations for physical configuration, installation, and setup. The guide contains information to help customers understand, plan for, manage, and get the most from their DS8000 investments.
This document provides installation and user guidance for IBM Tivoli Storage Manager for Databases Version 5.5, which provides data protection for Microsoft SQL Server. The document covers installing and configuring the software, how to perform backups and restores using both the graphical and command line interfaces, and how to schedule backups with the Tivoli Storage Manager scheduler. It also includes appendices with additional information on topics like silent installation, policy examples, restoring the master database, and messages.
Learn about the IBM Ported Tools for z/OS: PHP for z/OS Feature User’s Guide and Reference.This document presents the information you need to set up and use IBM Ported Tools for z/OS: PHP for z/OS Feature. This document is for the system programmers who run a z/OS system with z/OS UNIX System Services (z/OS UNIX), and for their users who use IBM Ported Tools for z/OS: PHP for z/OS Feature. On other open systems, some system programmer tasks may be done by an administrator. This document assumes the readers are familiar with z/OS systems and with the information for z/OS and its accompanying products. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit http://on.fb.me/LT4gdu to 'Like' the official Facebook page of IBM India Smarter Computing.
Learn about IBM Ported Tools for z/OS: Supplementary Toolkit for z/OS Feature User's Guide and Reference. This document presents the information you need to set up and use IBM Ported Tools for z/OS: Supplementary Toolkit for z/OS Feature.This document is for the system programmers who run a z/OS system with z/OS UNIX System Services (z/OS® UNIX), and for their users who use IBM Ported Tools for z/OS: Supplementary Toolkit for z/OS Feature. On other open systems, some system programmer tasks may be done by an administrator. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit http://bit.ly/KWh5Dx to 'Follow' the official Twitter handle of IBM India Smarter Computing.
This document provides release notes for IBM Tivoli Netcool/System Service Monitors and Netcool/Application Service Monitors version 4.0. Key items include over 40 problem fixes, several new subagents and features added, expanded platform support, and various improvements and changes.
This document provides an overview and instructions for configuring and using IBM Tivoli System Automation for z/OS V3R1. It discusses new features of V3R1 including integration with IBM Tivoli OMEGAMON and enhanced GDPS support. The document then covers tasks for setting up and customizing System Automation for z/OS such as defining VTAM configurations, the policy database, and automating startup tasks. It also provides guidance on using functions like the OMEGAMON interface, end-to-end automation capabilities, and managing SYSPLEXes with the Processor Operations feature.
Learn about IBM Ported Tools for z/OS User’s Guide. This document presents the information you need to set up and use the OpenSSH client. It also contains information about Xvfb. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit http://bit.ly/KWh5Dx to 'Follow' the official Twitter handle of IBM India Smarter Computing.
This document provides a 3-page overview of managing WebSphere Application Server for z/OS using Tivoli products. It introduces the automation blueprint for comprehensive management of WebSphere from performance, availability, and security. The document is organized to describe the WebSphere environment, IBM Tivoli Monitoring for Web Infrastructure for inside-out monitoring, and IBM Tivoli Monitoring for Transaction Performance for outside-in monitoring.
The document provides instructions and guidelines for installing and managing Citrix XenServer Dell Edition. It includes sections on installing and configuring XenServer, using XenCenter management software, configuring storage options like local disks and Dell storage arrays, backup and recovery procedures, best practices, and troubleshooting. The document aims to help users optimize the virtualization platform on Dell servers and storage.
This document provides guidance on implementing high availability for IBM Tivoli Workload Scheduler and IBM Tivoli Framework. It discusses different clustering technologies like IBM HACMP and Microsoft Cluster Server. It then describes how to set up Tivoli Workload Scheduler and Tivoli Framework in high availability configurations using these clustering solutions, including mutual takeover and hot standby scenarios. The document aims to provide best practices and tips for achieving high availability.
This document provides installation and upgrade instructions for Rational ClearCase Version 7.0.0 on Windows platforms. It includes information on planning the installation, system requirements, configuring the installation, creating a release area, installing servers and clients, and upgrading an existing installation. The document contains details on licensing, supported platforms, disk space needs, installation procedures, and post-installation configuration steps.
This document provides an installation and user's guide for Data Protection for SAP Version 5.5 for backing up SAP databases hosted on DB2. It covers concepts of data protection for SAP, developing a backup strategy, introducing the product, installing and configuring the product, using the Backup Object Manager and Administration Assistant, adjusting performance, balancing the system, reporting, and troubleshooting. The guide is intended for administrators implementing backup and recovery of SAP systems that use DB2 databases.
This document provides instructions for using IBM Tivoli Storage Manager (ITSM) with SysBack to enable bare machine recovery (BMR) for AIX systems. It discusses prerequisites, installation steps, and operational procedures for backing up systems to the ITSM server and restoring them from backup images. The document is intended to help users configure their AIX environments for disaster recovery using SysBack integrated with ITSM.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It covers installing and configuring the various Tivoli Monitoring components, including the database, Tivoli Enterprise Monitoring Server (TEMS), Tivoli Enterprise Portal Server, agents, and more. The guide also discusses backup strategies, uninstall procedures, and how to work with the Tivoli Enterprise Portal client.
This document provides a step-by-step guide for deploying IBM Tivoli Monitoring 6.1 in small to large environments. It discusses planning the installation, defining the architecture, creating deployment plans, installing the various Tivoli Monitoring components, and configuring the system. The guide also covers demonstrations of a single machine proof of concept installation and a small installation using DB2 Workgroup Edition.
The document is about end-to-end automation with IBM Tivoli System Automation for Multiplatforms. It provides an overview of IBM Tivoli System Automation for Multiplatforms V2.1 and IBM Tivoli System Automation for z/OS V3.1. It then presents three case study scenarios implementing end-to-end automation across different platforms using the products.
This document provides guidance on setting up a high availability SAP NetWeaver environment using SUSE Linux Enterprise Server and the SUSE Linux Enterprise High Availability Extension. It includes installing SAP NetWeaver with the Enqueue Replication Server and integrating the sap_suse_cluster_connector to provide application-level redundancy. The described configuration has passed all SAP certification tests for high availability.
This document discusses preparing for a migration to z/OS 1.13. It will cover the changed content in z/OS 1.13, ordering and delivery options, coexistence, migration, fall back and service policies. Requirements for both the driving and target systems will be highlighted, along with migration actions that can be performed now on the current z/OS release. The general availability date for z/OS 1.13 is planned for September 30, 2011.
The document provides instructions for accessing an IBM FTP server to download new versions and documentation for GDPS and RCMF products. There are separate directories for documentation, code, and fixes. Customers login with a userid and password specific to their installed product and download relevant files by setting the file transfer mode and specifying the remote and local files. If any issues occur, customers should contact GDPS support.
Hints for a successful hfs to zfs migrationsatish090909
IBM provides the following hints for a successful migration from Hierarchical File System (HFS) to zSeries File System (zFS):
1. Set up zFS by defining it in BPXPRMxx, creating the zFS PROC, and setting up the IOEFSPRM parameter file.
2. Define your first zFS filesystem by allocating a VSAM Linear Dataset and formatting it as a compatibility mode aggregate to contain the new filesystem.
3. Mount the new zFS filesystem using various methods like modifying BPXPRMxx, using the ISHELL mount command, or TSO mount command.
4. When migrating data, consider available DASD space,
This document provides copyright information and instructions for correctly citing the SAS 9.1.3 Foundation Configuration Guide for z/OS. It notes that no part of the publication may be reproduced without permission and lists the copyright owner. The document also contains a table of contents that outlines what is covered in each chapter of the Configuration Guide.
A catalog is a dataset that contains metadata about other datasets, allowing users to locate datasets without knowing their physical location. There are different types of catalogs including integrated catalog facility catalogs, VSAM catalogs, and OS CVOL catalogs. An integrated catalog facility catalog consists of a basic catalog structure (BCS) and a VSAM volume data set (VVDS). The BCS contains metadata about VSAM and non-VSAM datasets while the VVDS resides on each volume and contains extent and volume information for VSAM datasets on that volume.
The document provides an overview of data and storage management tools available in DFSMSdfp:
1) DFSMSdfp provides several access methods for organizing and processing data, including BPAM, BSAM, QSAM, VSAM, and OAM. It also supports older access methods like BDAM.
2) Access Method Services commands can be used to define, manipulate, and maintain data sets, volumes, and catalogs.
3) Utilities like IDCAMS and IEBCOPY can copy, move, dump, and restore data.
4) Callable services allow writing advanced application programs to manage storage.
5) Installation exits can customize DFSMS functions.
1) To access the TSO service at the University of Georgia, users must identify themselves by entering their USERID and password during the LOGON process.
2) The Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) is a component of TSO that facilitates interaction with the TSO service. This guide describes how to use ISPF/PDF.
3) Key conventions used in this guide include showing commands in UPPERCASE and information the user provides in lowercase. "Next to" indicates the character position immediately to the right of the indicating arrow.
This document describes a migration tool for moving files from the Hierarchical File System (HFS) to the zSeries File System (zFS) on z/OS. The tool includes programs for installing the migration software, customizing and running the migration process, and viewing help information. The tool allows users to migrate files while z/OS is running and supports migration processing on backlevel z/OS releases.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
14. Conventions and terminology used in this document
When this document refers to IBM® System z® servers without stating a specific
server, it refers to all of the following servers:
| v IBM zEnterpriseTM 114 (z114)
v IBM zEnterpriseTM 196 (z196)
v IBM System z10™ Enterprise Class (z10 EC)
v IBM System z10 Business Class (z10 BC)
v IBM System z9® Enterprise Class (z9 EC), formerly the IBM System z9 109
(z9-109)
v IBM System z9 Business Class (z9 BC)
v IBM eServer™ zSeries® 990 (z990)
v IBM eServer zSeries 890 (z890)
v IBM eServer zSeries 900 (z900)
v IBM eServer zSeries 800 (z800)
Important terms you should understand are:
v Migration. Migration is the first of two stages in an upgrade to a new release of
z/OS. (The second stage is exploitation.) During this stage you install your new
system with the objective of making it functionally compatible with the previous
system. After a successful migration, the applications and resources on the new
system function the same way (or similar to the way) they did on the old system
or, if that is not possible, in a way that accommodates the new system
differences so that existing workloads can continue to run. Migration does not
include exploitation of new functions except for new functions that are now
required.
v Exploitation. Exploitation is the second of two stages in an upgrade to a new
release of z/OS. (The first stage is migration.) During this stage you do
whatever customizing and programming are necessary to take advantage of
(exploit) the enhancements available in the new release.
v Coexistence. Coexistence is the situation in which two or more systems at
different software levels share resources. The resources could be shared at the
same time by different systems in a multisystem configuration, or they could be
shared over a period of time by the same system in a single-system
configuration.
Examples of coexistence are two different JES releases sharing a spool, two
different service levels of DFSMSdfp sharing catalogs, multiple levels of SMP/E
processing SYSMODS packaged to exploit the latest enhancements, or an older
level of the system using the updated system control files of a newer level (even
if new function has been exploited in the newer level).
The sharing of resources is inherent in multisystem configurations that involve
Parallel Sysplex® implementations. But other types of configurations can have
resource sharing too. Examples of configurations where resource sharing can
occur are:
– A single processor that is time-sliced to run different levels of the system,
such as during different times of the day
– A single processor running multiple images by means of logical partitions
(LPARs)
– Multiple images running on several different processors in either Parallel
Sysplex or non-Parallel Sysplex configurations
The way in which you make it possible for earlier-level systems to coexist with
the most current level is to install coexistence and fallback PTFs on the
earlier-level systems.
xii z/OS V1R13.0 Migration
15. v Fallback. Fallback is a return to the prior level of a system. Fallback can be
appropriate if you migrate to a new release and, during testing, encounter severe
problems that can be resolved by backing out the new release. By installing
coexistence and fallback PTFs on the “old” system before you migrate, the old
system can tolerate changes that were made by the new system during testing.
To identify the timing of migration actions, this document uses three types of
headings:
v Actions to perform Before installing z/OS V1R13. These are migration actions
that you perform on your current system, either because they require the current
system or because they are possible on the current system. You do not need the
z/OS V1R13 level of code to make these changes, and the changes do not
require the z/OS V1R13 level of code to run once they are made. Examples are
installing coexistence and fallback PTFs on your current system, discontinuing
use of hardware or software that will no longer be supported, and starting to
use existing functions that were optional on prior releases but required in z/OS
V1R13.
v Actions to perform before the first IPL of z/OS V1R13. These are migration
actions that you perform after you have installed z/OS V1R13 but before the
first time you IPL. These actions require the z/OS V1R13 level of code to be
installed but do not require it to be active. That is, you need the z/OS V1R13
programs, utilities, and samples in order to perform the migration actions, but
the z/OS V1R13 system does not have to be IPLed in order for the programs to
run. Examples are running sysplex utilities and updating the RACF® database
template.
It is possible to perform some of the migration actions in this category even
earlier. If you prepare a system on which you will install z/OS V1R13 by
making a clone of your old system, you can perform migration actions that
involve customization data on this newly prepared system before installing
z/OS V1R13 on it. Examples of such migration actions are updating
configuration files and updating automation scripts.
v Actions to perform after the first IPL of z/OS V1R13. These are migration
actions that you can perform only after you have IPLed z/OS V1R13. You need
a running z/OS V1R13 system to perform these actions. An example is issuing
RACF commands related to new functions. Note that the term “first IPL” does
not mean that you have to perform these actions after the very first IPL, but
rather that you need z/OS V1R13 to be active to perform the task. You might
perform the task quite a while after the first IPL.
Each migration action within the headings above is presented using the following
standard format:
v A title that identifies the migration action.
v Description. This is a brief description of the functional change that caused the
migration action.
v Element or feature. This is the name of the base element or optional feature that
changed.
v When change was introduced. This is the z/OS release in which the change was
introduced.
v Applies to migration from. The migration action is relevant if you are migrating
from this release.
About this document xiii
16. v Timing. This is when you should perform the migration action. There are three
categories: before installing z/OS, before first IPL, or after first IPL. (For SMP/E
there are two categories: after installing SMP/E but before starting to use it, and
after starting to use SMP/E.)
v Is the migration action required? This question refers to the migration action
identified by the title. The answer can be one of the following:
– Yes. The migration action is required in all cases.
– Yes, if... The migration action is required only in a certain case. Most of the
migration actions in this document are in this category.
– No, but recommended... The migration action is not required but is
recommended because it is a good programming practice, because it will be
required in the future, or because it resolves unacceptable system behavior
(such as poor usability or poor performance) even though resolution might
require a change in behavior.
v Target system hardware requirements. This is hardware required by the
functional change. It could be processor and peripheral devices; drivers,
engineering changes, or patches needed; or specific hardware functions that
must be active.
v Target system software requirements. This is software required by the functional
change. It could be z/OS optional features, software products, and PTFs that are
needed on the target system, as well as specific software functions that must be
active.
v Other system (coexistence or fallback) requirements. These are requirements
placed on an earlier release by the functional change in the new release. The
earlier release could be running on a system that shares resources (coexists) with
the new system or it could be the release from which you are migrating (and to
which you might want to fall back).
v Restrictions. These are any known limits on how the function can be used.
v System impacts. These are any known impacts of using the function, such as
increased storage or more time required to run.
v Related IBM Health Checker for z/OS check. These are IBM Health Checker for
z/OS checks available for the migration action.
v Steps to take. This is what you have to do to perform the migration action.
v Reference information. This is a pointer to additional information that helps you
perform the migration action.
The order in which the migration actions are presented does not imply importance
or chronology.
Related information
See z/OS Introduction and Release Guide for an introduction to z/OS and an
overview of the new functions in each release of z/OS.
See z/OS Planning for Installation for a summary of installation changes in each
release of z/OS, driving system hardware and software requirements, target
system hardware and software requirements, the coexistence-migration-fallback
policy, required releases of IBM middleware products, and considerations for
planning future installations.
To view, search, and print z/OS publications, go to the z/OS Internet Library at
http://www.ibm.com/eserver/zseries/zos/bkserv/.
xiv z/OS V1R13.0 Migration
20. - “Examine use of the CMDS ABEND command” on page 126.
- “Ensure Runtime Diagnostics is installed before invoking Predictive Failure
Analysis” on page 127.
– Communications Server
- “IP Services: Define a user ID for the system resolver with an associated
OMVS segment” on page 135.
- “IP Services: Ensure storage availability for ancillary input queue for
Enterprise Extender traffic” on page 137.
- “IP Services: Permit IKE daemon running in FIPS mode to use additional
ICSF services” on page 138.
- “IP Services: Understand and prepare for expanded Intrusion Detection
Services” on page 140.
- “IP Services: Ensure that the FTP user exit routine FTCHKPWD tolerates an
additional parameter” on page 141.
- “IP Services: Understand change in VIPARANGE security verification
processing” on page 142.
- “SNA Services: Ensure IVTCSM ASSIGN_BUFFER requests do not exceed
500 images for a single CSM buffer” on page 150.
- “IP Services: Review VIPARANGE definitions” on page 151.
- “SNA Services: Adjust to the relocation of the VTAM internal trace table”
on page 157.
– Cryptographic Services
- “ICSF: Ensure the CSFPUTIL utility is not used to initialize a PKDS” on
page 166.
- “System SSL: Ensure PKCS #11 tokens contain complete certificate chains”
on page 170.
- “ICSF: Ensure the expected master key support is available” on page 173.
– DFSMS
- “DFSMSdfp: Accommodate deletion of NOIMBED and NOREPLICAT
LISTCAT command attributes” on page 179.
- “DFSMSdfp: Update operator procedures and system automation for new
DADSM pre- and post-processing dynamic exits” on page 186.
- “DFSMSdfp: Update procedures that use IEBDSCPY alias name to access
IEBCOPY” on page 187.
- “DFSMShsm: Accommodate the changed default of PDA trace during
DFSMShsm startup” on page 194.
- “DFSMShsm: Accommodate the changed SETSYS FASTREPLICATION
command DATASETRECOVERY parameter default” on page 195.
- “DFSMShsm: Replace user-defined patch with new SETSYS
FASTREPLICATION command to enable ARC1809I messages” on page 196.
- “DFSMShsm: Review messages changed from I (informational) to E
(eventual action) type” on page 197.
- “DFSMShsm: Remove patch that prevents SMS MVT chain rebuild” on
page 198.
- “DFSMShsm: Update operator procedure in the Multicluster CDS
environment” on page 199.
- “DFSMSdfp: Accommodate 64-bit and AR mode rules enforcement in
DFSMS macros” on page 204.
- “DFSMSdfp: Run OAM configuration database migration job” on page 205.
xviii z/OS V1R13.0 Migration
21. - “DFSMSdss: Accommodate Catalog Search Interface default change” on
page 207.
- “DFSMShsm: Stop using the HOLD command to quiesce activity prior to
control data set backup” on page 208.
– Distributed File Service
- “zFS: Accommodate new DASD space requirements” on page 215.
- “zFS: Copy cloned file systems to a compatibility mode aggregate” on page
217.
- “zFS: Copy data from zFS multi-file system aggregates to zFS compatibility
mode aggregates” on page 218.
- “zFS: Ensure sysplex=filesys is available on all zFS R11 and R12 systems in
a shared file system environment” on page 219.
- “zFS: Verify virtual storage usage” on page 222.
- “DCE/DFS: Disable DFS Client initialization” on page 224.
– Infoprint Server
- “Update or remove the region size in the AOPSTART startup procedure”
on page 232.
– JES3
- “Modify code that depends on the format of suppressed split messages in
the DLOG” on page 245.
- “Avoid redundant *S main,FLUSH command in response to XCF messages”
on page 246.
– Language Environment
- “Convert to CEEPRMxx to set system-level default runtime options” on
page 251.
– RMF
- “Check your automation for Monitor III messages ERB812I and ERB813I”
on page 259.
- “Determine need of SMF data collection for Postprocessor Serialization
Delay report” on page 261.
– SDSF
- “Update configuration for sysplex support” on page 266.
- “Review colors on the OPERLOG panel” on page 267.
- “Set the format of device names on the Punch and Reader panels” on page
268.
– Security Server
- “Normalize user names specified as X.500 distinguished names in
distributed identity filters” on page 273.
– z/OS UNIX
- “Update invocations of /usr/sbin/mount commands” on page 289.
- “Update invocations of /usr/sbin/unmount commands” on page 290.
- “Review programs that invoke the BPX1EXM/BPX4EXM callable service”
on page 291.
- “Update invocations of MOUNT statements in the BPXPRMxx parmlib
member” on page 298.
- “Accommodate changes to support read-only z/OS root for the cron, mail,
and uucp utilities” on page 299.
Summary of changes xix
22. - “Discontinue use of invalid REXX variables in z/OS UNIX syscalls” on
page 302.
Changed information:
v z/OS Management Facility (z/OSMF) migration actions are located in
"Migrating from an earlier release of z/OSMF" in IBM z/OS Management Facility
Configuration Guide.
v “Elements and features that do not have migration actions” on page 5 has been
updated.
v “Update your check customization for modified IBM Health Checker for z/OS
checks” on page 28 has been updated to reflect new, changed, and deleted IBM
for Health Checker for z/OS checks.
v Table 3 on page 30 has been updated.
v Table 4 on page 36 has been updated.
v “Accommodate ISC-3, PSC, ESCON, FICON, OSA-Express2, and dial-up modem
changes introduced with the IBM zEnterprise 196 (z196) server and the IBM
zEnterprise 114 (z114) server” on page 42 has been updated to include
information about the new IBM zEnterprise 114 (z114) server.
v The z/OS V1R12 migration action, "Migrate to an IBM zEnterprise 196 (z196)
server," has been undated to include information about the new IBM zEnterprise
114 (z114 server) and is now titled, “Migrate to an IBM zEnterprise server” on
page 47.
v "IP Services: Migrate from DNS BIND 9.2.0" and replaced with “IP Services:
Migrate from BIND 9.2.0” on page 139.
v “Determine the impact of added and changed runtime options” on page 249 has
been updated.
v Also, see additional changes indicated by the change bar | in the margin.
Deleted information:
v Approximately 80 migration actions have been deleted because they applied to
migrations from z/OS V1R10, and that release is not supported for migration to
z/OS V1R13.
v z/OS Management Facility (z/OSMF) migration actions can be found in
"Migrating from an earlier release of z/OSMF" in IBM z/OS Management Facility
Configuration Guide.
This document contains terminology, maintenance, and editorial changes. Technical
changes or additions to the text and illustrations are indicated by a vertical line to
the left of the change.
xx z/OS V1R13.0 Migration
24. 6. Prepare target system hardware and software. During this step, perform the
migration actions identified by headings that say actions to perform before
the first IPL of z/OS V1R13. (Again, not all of the actions are required. Some
depend on your environment, configuration, and workload, and are identified
accordingly.)
7. IPL the new z/OS V1R13 system with your updated customization and
configuration files.
8. Perform any migration actions identified by headings that say actions to
perform after the first IPL of z/OS V1R13. (Again, not all of the actions are
required. Some depend on your environment, configuration, and workload,
and are identified accordingly.)
Use IBM Health Checker for z/OS to assist with some migration actions. See
“Using IBM Health Checker for z/OS for migration checking.”
9. Deploy z/OS V1R13 to other systems within a sysplex, data center, and
enterprise.
The migration is now complete.
10. When you are confident that a system, or in some cases all systems in a
sysplex, are not going to fall back to z/OS V1R12 or z/OS V1R11 exploit the
functions introduced in z/OS V1R13.
11. Deploy this exploitation on other systems (again within a sysplex, data center,
and eventually enterprise).
Using IBM Health Checker for z/OS for migration checking
Beginning with z/OS V1R10, the IBM Health Checker for z/OS infrastructure is
being exploited for migration purposes. Checks are being added to help you
determine the applicability of various migration actions. Before you migrate to
your new z/OS release, you should use these new checks to assist with migration
planning. After you migrate, you should rerun them to verify that the migration
actions were successfully performed. As with any IBM Health Checker for z/OS
check, no updates are made to the system. These new migration checks only report
on the applicability of specific migration actions on a system, and only on the
currently active system.
The migration checks are very similar to the other checks provided by IBM Health
Checker for z/OS. The only differences are:
v The names of migration checks follow the convention
ZOSMIGVvvRrr_component_program_name (or, for ICSF,
ICSFMIGnnnn_component_program_name). Notice the “MIG” characters followed
immediately by the release identifier. This convention tells you that the check
helps with migration and it tells you the release in which the migration action
was introduced. If the release in which the migration action was introduced is
not known, the name will be ZOSMIGREC.
v By default, migration checks are inactive. This is because you might not want to
know about migration actions during nonmigration periods.
System REXX health check considerations
All exploiters of the System REXX support in z/OS require that the System REXX
customization be performed. Using the IBM Health Checker for z/OS health
checks is one example of possible System REXX exploitation. In particular, any
compiled REXX execs must have the proper runtime support available from the
Alternate Library for REXX (available in z/OS since V1R9) or from the IBM
Library for REXX on zSeries (5695-014). Several IBM Health Checker for z/OS
2 z/OS V1R13.0 Migration
25. migration health checks have been written in compiled System REXX. These health
checks rely upon the System REXX customization and runtime activities being
completed. If System REXX (and the security environment that System REXX
requires) have not been properly customized, then System REXX health checks will
not execute successfully.
v For System REXX customization activities, refer to "System REXX" in z/OS MVS
Programming: Authorized Assembler Services Guide.
v For compiled REXX exec runtime availability, see "Alternate Library for REXX
Customization Considerations" in z/OS Program Directory, or refer to product
documentation accompanying IBM Library for REXX on zSeries.
As stated previously, migration checks are intended to be used on your current
z/OS release and then again after you have migrated to your new z/OS release.
The steps you might follow in each of these two scenarios are shown below.
On your current z/OS release:
1. Install the latest migration checks. Review all the latest health checks (for both
best practices and migration) by using the functional PSP bucket HCHECKER
(which is SMP/E FIXCAT IBM.Function.HealthChecker). If you want to see all
IBM Health Checker for z/OS checks see http://www.ibm.com/systems/z/os/
zos/hchecker/check_table.html.
You might want to install the PTFs during a regular service window so that an
IPL is scheduled afterwards. Checks are often added by a function when it is
started or restarted, so you might find that installing the PTFs before a
scheduled IPL works best for you. Additional migration checks can be added at
different times, so having all the latest ones installed prior to making your
migration plans is recommended.
2. Activate the migration checks appropriate to your migration path. Because the
naming convention for migration checks indicates which release introduced the
corresponding migration actions, you can activate just the checks appropriate
for your migration path. Using SDSF (or another method for viewing checks,
such as filters), you can view ahead of time which migration checks you have
available on your system. For example, if you are migrating from z/OS V1R11
to z/OS V1R13 you need to activate the migration checks for changes that
occurred in both z/OS V1R12 and z/OS V1R13. If you are migrating from
z/OS V1R12 to z/OS V1R13, you only need to activate the migration checks for
changes that occurred in z/OS V1R13. There are many ways to make a check
active, as well as many ways of using wildcards to include specific checks.
Here are some examples of using the MODIFY command to make checks
active:
v F HZSPROC,ACTIVATE,CHECK=(IBM*,*MIG*)
v F HZSPROC,ACTIVATE,CHECK=(IBM*,ICSFMIG*)
v F HZSPROC,ACTIVATE,CHECK=(IBM*,ZOSMIGV1R12)
Remember that for z/OS, two naming conventions are used: one for ICSF (that
starts with ICSFMIGnnnn) and one for the rest of z/OS (that starts with
ZOSMIGVvvRrr). Use a wildcard filter that includes the intended migration
checks.
3. Review the migration check output and rerun checks as appropriate. Any exceptions
should be addressed in your migration plan. If you can complete the migration
action prior to moving to the new z/OS release, you can rerun the check to
verify that it was completed correctly on your current system.
Chapter 1. Introduction 3
26. 4. Deactivate the migration checks if you desire. If you no longer desire to have the
migration checks active, you can deactivate them similar to the way you
activated them. For example:
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,*MIG*)
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,ICSFMIG*)
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,ZOSMIGV1R12)
After you have migrated to the new z/OS release, the steps are similar:
1. Install the latest migration checks. New migration checks might be available for
your new z/OS system since you installed it. Therefore, review all the latest
health checks (for both best practices and migration) by using the functional
PSP bucket HCHECKER (which is SMP/E FIXCAT
IBM.Function.HealthChecker). If you want to see all IBM Health Checker for
z/OS checks that are available, see http://www.ibm.com/systems/z/os/zos/
hchecker/check_table.html.
2. Activate the migration checks appropriate to your migration path. For migration
verification, activate the checks appropriate on the release you are migrating
from, migrating through, and migrating to. For example, if you are migrating
from z/OS V1R11 to z/OS V1R13, you need to activate the migration checks
for changes that occurred in both z/OS V1R12 and z/OS V1R13. If you are
migrating from z/OS V1R12 to z/OS V1R13, you only need to activate the
migration checks for changes that occurred in z/OS V1R13. Here are some
examples of using the MODIFY command to make checks active. (These are the
same activation commands shown previously.)
v F HZSPROC,ACTIVATE,CHECK=(IBM*,*MIG*)
v F HZSPROC,ACTIVATE,CHECK=(IBM*,ICSFMIG*)
v F HZSPROC,ACTIVATE,CHECK=(IBM*,ZOSMIGV1R12)
3. Review the migration check output and rerun checks as appropriate. Any exceptions,
which could indicate that a migration action was not performed correctly,
should be addressed. Rerun the check after the corrections have been made.
4. Deactivate the migration checks. Once your migration verification is complete,
deactivate the migration checks similar to the way you activated them. For
example (using the same deactivation commands shown previously):
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,*MIG*)
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,ICSFMIG*)
v F HZSPROC,DEACTIVATE,CHECK=(IBM*,ZOSMIGV1R12)
Within this document, the migration actions that have checks are clearly identified
within the migration actions. All of the checks are made by IBM Health Checker
for z/OS but, as stated earlier, some of the checks are the new migration checks
(identified by names that start with ZOSMIGVvvRrr or ICSFMIGnnnn) and others
are regular health checks.
Note that not all migration actions in this document are addressed by checks;
many migration actions do not lend themselves to programmatic checking.
Therefore, use this document to prepare your migration plan and do not rely solely
on checks.
4 z/OS V1R13.0 Migration
27. EPSPT replaced by FIXCAT and REPORT MISSINGFIX
IBM removed the Enhanced PSP Tool (EPSPT), host compare program, and the
associated extract files from the IBM Technical Support web site
(http://www14.software.ibm.com/webapp/set2/psp/srchBroker), effective 31
December 2010. The Enhanced PSP Tool's function has been replaced by the
addition of FIXCAT (fix category) information to Enhanced HOLDDATA and the
REPORT MISSINGFIX function introduced in z/OS V1R10 SMP/E, which offers
distinct advantages over the Enhanced PSP Tool. This SMP/E function is also
available for all supported releases of z/OS in SMP/E for z/OS V3R6 (5655-G44),
which you can order separately.
| z/OS Management Facility
| IBM z/OS Management Facility (z/OSMF) provides system programmers with a
| framework for managing various aspects of a z/OS system through a web browser
| interface. By streamlining some traditional tasks and automating others, z/OSMF
| can help to simplify the day-to-day operations and administration of a z/OS
| system. For more information about z/OSMF, see www.ibm.com/systems/z/os/
| zos/zosmf/.
| For information about z/OSMF migration steps, see "Migrating from an earlier
| release of z/OSMF" in IBM z/OS Management Facility Configuration Guide.
Elements and features that do not have migration actions
The following z/OS V1R13 elements and features do not have migration actions
and thus are not discussed:
v Alternate Library for REXX
v BDT
v BDT File-to-File
v BDT SNA NJE
v BookManager® BUILD
v BookManager READ
| v CIM
v Communications Server Security Level 3
v EREP
v ESCON® Director Support
v FFST
v GDDM
v GDDM-PGF
v GDDM-REXX
v HCD
| v HCM
v HLASM
v HLASM Toolkit
v IBM HTTP Server
v ICKDSF
| v Integrated Security Services
v ISPF
v Metal C Runtime Library
v MICR/OCR
v NFS
v Run-Time Library Extensions
v TIOC
| v z/OS IBM TDS
Chapter 1. Introduction 5
28. v z/OS Security Level 3
v 3270 PC File Transfer Program
6 z/OS V1R13.0 Migration