DOCSLIB.ORG

Z/OS V2R4.0 Communications Server: New Function Summary Summary of Changes for New Function Summary

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Z/OS V2R4.0 Communications Server: New Function Summary Summary of Changes for New Function Summary z/OS Communications Server 2.4 New Function Summary IBM GC27-3664-40 Note: Before using this information and the product it supports, be sure to read the general information under “Notices” on page 203. This edition applies to Version 2 Release 4 of z/OS® (5650-ZOS), and to subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2021-06-21 © Copyright International Business Machines Corporation 2000, 2021. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables................................................................................................................. vii About this document............................................................................................xv Who should read this document................................................................................................................ xv How this document is organized................................................................................................................ xv How to use this document.........................................................................................................................xvi How to contact IBM service.................................................................................................................xvi Conventions and terminology that are used in this information.............................................................. xvi Prerequisite and related information....................................................................................................... xvii Summary of changes for New Function Summary............................................... xxiii Changes made in z/OS Version 2 Release 4............................................................................................xxiii Changes made in z/OS Version 2 Release 3............................................................................................xxiv Changes made in z/OS Version 2 Release 2, as updated June 2017......................................................xxv Changes made in z/OS Version 2 Release 2, as updated September 2016........................................... xxv Changes made in z/OS Version 2 Release 2, as updated March 2016................................................... xxv Changes made in z/OS Version 2 Release 2............................................................................................ xxv Chapter 1. Planning to use new functions...............................................................1 Introduction to z/OS Communications Server............................................................................................ 1 Determining which documents to use when migrating.............................................................................. 1 IP encryption features................................................................................................................................. 3 Planning checklist........................................................................................................................................ 3 TCP/IP packaging process........................................................................................................................... 4 MVS data sets......................................................................................................................................... 4 File system files...................................................................................................................................... 7 Defining SNA data sets.................................................................................................................................7 Data sets containing information for z/OS V2R4 Communications Server.........................................11 Chapter 2. Roadmap to functions......................................................................... 21 Chapter 3. V2R4 new function summary...............................................................25 Hardware support...................................................................................................................................... 25 Shared Memory Communications - Direct multiple IP subnet support (SMC-Dv2)...........................25 Communications Server support for OSA-Express7S 25 GbE features..............................................27 Communications Server support for 25 GbE RoCE Express2 features.............................................. 29 Communications Server QDIO display enhancements.......................................................................29 Usability and skills..................................................................................................................................... 30 HiperSockets Converged Interface support........................................................................................ 30 Scalability and performance......................................................................................................................33 zERT Aggregation recording interval....................................................................................................33 Inbound Workload Queueing (IWQ) support for IBM z/OS Container Extensions.............................34 Sysplex notification of TCP/IP stack join or leave............................................................................... 36 Network support for z/OS Container Extensions.................................................................................37 IWQ support for IPSec......................................................................................................................... 39 Enhancing security.....................................................................................................................................41 IBM Health Checker for use of native TLS/SSL support for DCAS...................................................... 41 IBM Health Checker for use of native TLS/SSL support for the FTP server........................................42 IBM Health Checker for use of native TLS/SSL support for the TN3270 server.................................44 iii Sysplex Autonomics for IPSec............................................................................................................. 44 IBM zERT Network Analyzer database administration enhancements.............................................. 46 AT-TLS support for TLS v1.3.................................................................................................................47 z/OS Encryption Readiness Technology (zERT) aggregation.............................................................. 51 IBM zERT Network Analyzer................................................................................................................ 54 TN3270E Telnet server Express Logon Feature support for Multi-Factor Authentication.................56 Application development...........................................................................................................................57 SMTPD compatibility enhancements for CSSMTP...............................................................................57 Communications Server resolver enhancements............................................................................... 58 Code page enhancements for CSSMTP............................................................................................... 59 Chapter 4. Communications Server interface changes for z/OS V2R4.................... 61 Communications Server IP interface changes..........................................................................................61 PROFILE.TCPIP configuration file........................................................................................................ 62 Configuration files................................................................................................................................ 64 RACF interfaces.................................................................................................................................... 68 Operator commands............................................................................................................................ 69 TSO commands.................................................................................................................................... 72 z/OS UNIX commands..........................................................................................................................74 Application programming interfaces and network management interfaces......................................76 Environment variables..........................................................................................................................80 Socket APIs.......................................................................................................................................... 80 IPCS subcommands............................................................................................................................. 80 SNMP MIB modules............................................................................................................................. 82 User exits..............................................................................................................................................83 Application
Load more

Recommended publications
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
    [Show full text]
  • SYSTEM V RELEASE 4 Migration Guide
    - ATlaT UN/~ SYSTEM V RELEASE 4 Migration Guide UNIX Software Operation Copyright 1990,1989,1988,1987,1986,1985,1984,1983 AT&T All Rights Reserved Printed In USA Published by Prentice-Hall, Inc. A Division of Simon & Schuster Englewood Cliffs, New Jersey 07632 No part of this publication may be reproduced or transmitted in any form or by any means-graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in any medium, tap­ ing, by any computer or information storage and retrieval systems, etc., without prior permissions in writing from AT&T. IMPORTANT NOTE TO USERS While every effort has been made to ensure the accuracy of all information in this document, AT&T assumes no liability to any party for any loss or damage caused by errors or omissions or by state­ ments of any kind in this document, its updates, supplements, or special editions, whether such er­ rors are omissions or statements resulting from negligence, accident, or any other cause. AT&T furth­ er assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this docu­ ment. AT&T disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. AT&T makes no representation that the interconnection of products in the manner described herein will not infringe on existing or future patent rights, nor do the descriptions contained herein imply the granting or license to make, use or sell equipment constructed in accordance with this description.
    [Show full text]
  • Fast Linux I/O in the Unix Tradition
    — preprint only: final version will appear in OSR, July 2008 — PipesFS: Fast Linux I/O in the Unix Tradition Willem de Bruijn Herbert Bos Vrije Universiteit Amsterdam Vrije Universiteit Amsterdam and NICTA [email protected] [email protected] ABSTRACT ory wall” [26]). To improve throughput, it is now essential This paper presents PipesFS, an I/O architecture for Linux to avoid all unnecessary memory operations. Inefficient I/O 2.6 that increases I/O throughput and adds support for het- primitives exacerbate the effects of the memory wall by in- erogeneous parallel processors by (1) collapsing many I/O curring unnecessary copying and context switching, and as interfaces onto one: the Unix pipeline, (2) increasing pipe a result of these cache misses. efficiency and (3) exploiting pipeline modularity to spread computation across all available processors. Contribution. We revisit the Unix pipeline as a generic model for streaming I/O, but modify it to reduce overhead, PipesFS extends the pipeline model to kernel I/O and com- extend it to integrate kernel processing and complement it municates with applications through a Linux virtual filesys- with support for anycore execution. We link kernel and tem (VFS), where directory nodes represent operations and userspace processing through a virtual filesystem, PipesFS, pipe nodes export live kernel data. Users can thus interact that presents kernel operations as directories and live data as with kernel I/O through existing calls like mkdir, tools like pipes. This solution avoids new interfaces and so unlocks all grep, most languages and even shell scripts.
    [Show full text]
  • Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package Streams-0.9.2.4
    Linux Fast-STREAMS Installation and Reference Manual Version 0.9.2 Edition 4 Updated 2008-10-31 Package streams-0.9.2.4 Brian Bidulock <[email protected]> for The OpenSS7 Project <http://www.openss7.org/> Copyright c 2001-2008 OpenSS7 Corporation <http://www.openss7.com/> Copyright c 1997-2000 Brian F. G. Bidulock <[email protected]> All Rights Reserved. Published by OpenSS7 Corporation 1469 Jefferys Crescent Edmonton, Alberta T6L 6T1 Canada This is texinfo edition 4 of the Linux Fast-STREAMS manual, and is consistent with streams 0.9.2. This manual was developed under the OpenSS7 Project and was funded in part by OpenSS7 Corporation. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the same conditions as for modified versions. i Short Contents Preface ::::::::::::::::::::::::::::::::::::::::::::::::: 1 Quick Start Guide :::::::::::::::::::::::::::::::::::::::: 9 1 Introduction :::::::::::::::::::::::::::::::::::::::: 15 2 Objective ::::::::::::::::::::::::::::::::::::::::::: 17 3 Reference ::::::::::::::::::::::::::::::::::::::::::: 21 4 Development ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Introduction to the Linux for HPC
    Introduction to the Linux for HPC Basic Linux for Beginner HPC Users Purpose of This Lecture • Fundamentals of using Linux and Linux-like systems on HPC systems • History of Linux • Shell and basic commands • File, data and process management and utilities History of Linux Linux in the Real World 95% Top500 are Linux-like Operating System # of Systems Percentage Linux 456 91.20% Unix 22 4.40% Windows 6 1.20% BSD Based 1 0.20% Mixed 15 3.00% Unix A Little History • Q: How old is Unix (5, 10, 20 years, or greater)? A: > 40 Years • Unix dates back to 1969 with a group at Bell Laboratories • The original Unix operating system was written in assembler • First 1972 Unix installations had 3 users and a 500KB disk DEC PDP-11, 1972 Linux Bringing Unix to the Desktop • Unix was very expensive • MINIX, tried but was not a full port • An open source solution was needed! 1990’s Movers and Shakers Richard Stallman, father of the GNU Project Linus Torvalds What is Linux? • Linux is a clone of the Unix operating system written from scratch by Linus Torvalds with assistance from developers around the globe (technically speaking, Linux is not Unix) • Torvalds uploaded the first version - 0.01 in September 1991 • Only about 2% of the current Linux kernel is written by Torvalds himself but he remains the ultimate authority on what new code is incorporated into the Linux kernel. • Developed under the GNU General Public License , the source code for Linux is freely available • A large number of Linux-based distributions exist (for free or purchase) Why use LINUX? • Performance: as we’ve seen, supercomputers generally run Linux; rich-multi user environment • Functionality: a number of community driven scientific applications and libraries are developed under Linux (molecular dynamics, linear algebra, fast-fourier transforms, etc).
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • Fstream: Managing Flash Streams in the File System
    FStream: Managing Flash Streams in the File System Eunhee Rho, Kanchan Joshi, Seung-Uk Shin, Nitesh Jagadeesh Shetty, Joo-Young Hwang, Sangyeun Cho, Daniel DG Lee, and Jaeheon Jeong, Samsung Electronics. Co., Ltd. https://www.usenix.org/conference/fast18/presentation/rho This paper is included in the Proceedings of the 16th USENIX Conference on File and Storage Technologies. February 12–15, 2018 • Oakland, CA, USA ISBN 978-1-931971-42-3 Open access to the Proceedings of the 16th USENIX Conference on File and Storage Technologies is sponsored by USENIX. FStream: Managing Flash Streams in the File System Eunhee Rho, Kanchan Joshi, Seung-Uk Shin, Nitesh Jagadeesh Shetty Joo-Young Hwang, Sangyeun Cho, Daniel DG Lee, Jaeheon Jeong Samsung Electronics Co., Ltd. Abstract out issue [3,7]. To the same end, we focus on how to take The performance and lifespan of a solid-state drive advantage of the multi-streamed SSD mechanism [8]. (SSD) depend not only on the current input workload This mechanism opens up a way to dictate data place- but also on its internal media fragmentation formed over ment on an SSD’s underlying physical media, abstracted time, as stale data are spread over a wide range of phys- by streams. In principle, if the host system perfectly ical space in an SSD. The recently proposed streams maps data having the same lifetime to the same streams, gives a means for the host system to control how data are an SSD’s write amplification becomes one, completely placed on the physical media (abstracted by a stream) eliminating the media fragmentation problem.
    [Show full text]
  • Veritas Backup Exec from Arcserve Netware.Pdf
    for NetWare Using v8.5 of VERITAS Backup Exec™ for NetWare’s Enhanced ARCserveIT Tape Read Feature With this release, Backup Exec for NetWare extends its ability to read ARCserveIT tapes, allowing you to more easily migrate from ARCserveIT to Backup Exec and to restore data from ARCserveIT tapes. Backup Exec will read: • ARCserveIT for NetWare versions 4.x, 5.x, and 6.x • ARCserveIT for Windows NT version 6.x • ARCserveIT’s native tape format • ARCserveIT’s embedded SMS tape format How the Enhanced ARCserveIT Tape Read Works When backing up a NetWare server, ARCserveIT 6.x by default includes Novell’s SMS data streams within the ARCserveIT format, allowing ARCserveIT to get its data stream from a Novell TSA. ARCserveIT then packages this data stream within the ARCserveIT format and places this data on tape. To read the data, Backup Exec unpackages the original TSA data and sends it back to the Novell TSA for interpretation. The NetWare server files and directories backed up by ARCserveIT can thus be fully restored by Backup Exec. Special Limitations If the default for ARCserveIT is changed so that ARCserveIT does not use SMS for backing up NetWare servers, the backup sets on the tape will be in ARCserveIT’s native format. Backup Exec will restore file and directory data, but will not always restore the long name for files. Other limitations are that Backup Exec cannot read the following: • ARCserveIT backup sets that are software compressed, software encrypted, or interleaved • ARCserveIT backups of NDS data sets • ARCserveIT backups of the NT registry • ARCserveIT backups of Microsoft Exchange or Microsoft SQL data Note NDS backups rapidly become out of date; therefore, you probably would not be restoring ARCserveIT backups of NDS data using Backup Exec.
    [Show full text]
  • FR-1998-01-27.Pdf
    1±27±98 Tuesday Vol. 63 No. 17 January 27, 1998 Pages 3791±4150 Briefings on how to use the Federal Register For information on briefings in Washington, DC, see announcement on the inside cover of this issue. Now Available Online via GPO Access Free online access to the official editions of the Federal Register, the Code of Federal Regulations and other Federal Register publications is available on GPO Access, a service of the U.S. Government Printing Office at: http://www.access.gpo.gov/nara/index.html For additional information on GPO Access products, services and access methods, see page II or contact the GPO Access User Support Team via: ★ Phone: toll-free: 1-888-293-6498 ★ Email: [email protected] federal register 1 II Federal Register / Vol. 63, No. 17 / Tuesday, January 27, 1998 SUBSCRIPTIONS AND COPIES PUBLIC Subscriptions: Paper or fiche 202±512±1800 Assistance with public subscriptions 512±1806 General online information 202±512±1530; 1±888±293±6498 FEDERAL REGISTER Published daily, Monday through Friday, (not published on Saturdays, Sundays, or on official holidays), Single copies/back copies: by the Office of the Federal Register, National Archives and Paper or fiche 512±1800 Records Administration, Washington, DC 20408, under the Federal Assistance with public single copies 512±1803 Register Act (49 Stat. 500, as amended; 44 U.S.C. Ch. 15) and FEDERAL AGENCIES the regulations of the Administrative Committee of the Federal Subscriptions: Register (1 CFR Ch. I). Distribution is made only by the Superintendent of Documents, U.S. Government Printing Office, Paper or fiche 523±5243 Washington, DC 20402.
    [Show full text]
  • COS 318: Operating Systems I/O Device Interactions and Drivers
    Topics COS 318: Operating Systems u So far: l Management of CPU and concurrency l Management of main memory and virtual memory I/O Device Interactions and u Next: Management of the I/O system Drivers l Interacting with I/O devices l Device drivers Jaswinder Pal Singh l Storage Devices Computer Science Department Princeton University u Then, File Systems l File System Structure (http://www.cs.princeton.edu/courses/cos318/) l Naming and Directories l Efficiency/Performance l Reliability and Protection 2 Input and Output Revisit Hardware u A computer u Compute hardware CPU l CPU cores and caches CPU l Computation (CPU, memory hierarchy) CPUCPU CPU l Memory $ l Move data into and out of a system (locketween I/O devices Chip l I/O and memory hierarchy) l Controllers and logic Memory I/O bridge u Challenges with I/O devices I/O bus l Different categories with different characteristics: storage, u I/O Hardware networking, displays, keyboard, mouse ... l I/O bus or interconnect l Large number of device drivers to support l I/O device l I/O controller or adapter l Device drivers run in kernel mode and can crash systems • Often on parent board Network u Goals of the OS • Cable connects it to device • Often using standard interfaces: IDE, l Provide a generic, consistent, convenient and reliable way to SATA, SCSI, USB, FireWire… access I/O devices • Has registers for control, data signals • Processor gives commands and/or l Achieve potential I/O performance in a system data to controller to do I/O • Special I/O instructions (w.
    [Show full text]
  • Using C-Kermit 2Nd Edition
    << Previous file Chapter 1 Introduction An ever-increasing amount of communication is electronic and digital: computers talking to computers Ð directly, over the telephone system, through networks. When you want two computers to communicate, it is usually for one of two reasons: to interact directly with another computer or to transfer data between the two computers. Kermit software gives you both these capabilities, and a lot more too. C-Kermit is a communications software program written in the C language. It is available for many different kinds of computers and operating systems, including literally hundreds of UNIX varieties (HP-UX, AIX, Solaris, IRIX, SCO, Linux, ...), Digital Equipment Corporation (Open)VMS, Microsoft Windows NT and 95, IBM OS/2, Stratus VOS, Data General AOS/VS, Microware OS-9, the Apple Macintosh, the Commodore Amiga, and the Atari ST. On all these platforms, C-Kermit's services include: • Connection establishment. This means making dialup modem connections or (in most cases) network connections, including TCP/IP Telnet or Rlogin, X.25, LAT, NET- BIOS, or other types of networks. For dialup connections, C-Kermit supports a wide range of modems and an extremely sophisticated yet easy-to-use dialing directory. And C-Kermit accepts incoming connections from other computers too. • Terminal sessions. An interactive terminal connection can be made to another com- puter via modem or network. The Windows 95, Windows NT, and OS/2 versions of C-Kermit also emulate specific types of terminals, such as the Digital Equipment Cor- poration VT320, the Wyse 60, or the ANSI terminal types used for accessing BBSs or PC UNIX consoles, with lots of extras such as scrollback, key mapping, printer con- trol, colors, and mouse shortcuts.
    [Show full text]
  • Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18
    Presentation on Principles of Distributed Embedded Systems (Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18) Prepared by, Dr. S. Vinoth Associate Professor UNIT - I REAL TIME ENVIRONMENT 2 UNIT - I REAL-TIME ENVIRONMENT .Real-time computer system requirements .classification of real time systems .simplicity, global time .internal and external clock synchronization .real time model. Real time communication .temporal relations, dependability .power and energy awareness .real time communication .event triggered .rate constrained .time triggered. 3 What is an Embedded system? 4 What is a real-time system? . A real-time system is any information processing system which has to respond to externally generated input stimuli within a finite and specified period –the correctness depends not only on the logical result but also the time it was delivered –failure to respond is as bad as the wrong response! . The computer is a component in a larger engineering system => EMBEDDED COMPUTER SYSTEM 99% of all processors are for the embedded systems market 5 Terminology • Hard real-time — systems where it is absolutely imperative that responses occur within the required deadline. E.g. Flight control systems. • Soft real-time — systems where deadlines are important but which will still function correctly if deadlines are occasionally missed. E.g. Data acquisition system. • Real real-time — systems which are hard real-time and which the response times are very short. E.g. Missile guidance system. • Firm real-time — systems which are soft real-time but in which there is no benefit from late delivery of service. A single system may have all hard, soft and real real-time subsystems In reality many systems will have a cost function associated with missing each deadline.
    [Show full text]