DOCSLIB.ORG

Z/OS Communications Server Version 2.Release 4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Z/OS Communications Server Version 2.Release 4 z/OS Communications Server Version 2.Release 4 SNA Diagnosis Volume 2: FFST Dumps and the VIT IBM GC27-3668-40 Note: Before using this information and the product it supports, be sure to read the general information under “Notices” on page 847. 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, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures.................................................................................................................. v Tables................................................................................................................. vii About this document.............................................................................................ix Summary of changes for SNA Diagnosis Volume 2: FFST Dumps and the VIT..........xv Chapter 1. Using FFST dumps................................................................................ 1 Chapter 2. Using the VTAM internal trace................................................................7 Appendix A. FFST operations............................................................................... 27 Appendix B. VTAM internal trace (VIT) record descriptions................................. 221 Appendix C. Internal topology traces................................................................. 775 Appendix D. First Failure Support Technology (FFST) probes.............................. 799 Appendix E. Communications storage manager (CSM) FFST probes.................... 841 Appendix F. Architectural specifications.............................................................843 Appendix G. Accessibility.................................................................................. 845 Notices..............................................................................................................847 Bibliography......................................................................................................851 Index................................................................................................................ 857 Communicating your comments to IBM.............................................................. 869 iii iv Figures 1. Sample VTAM FFST console listing............................................................................................................... 4 2. Unformatted VIT records in dump output (MODE=INT)............................................................................ 19 3. TRS common topology trace table with two buffers allocated................................................................793 v vi Tables 1. Trace options of the OPTION operand........................................................................................................11 2. Exception conditions always traced by the VIT..........................................................................................15 3. VIT options and the records they create (API - LOCK)...............................................................................16 4. VIT options and the records they create (MSG - XCF)............................................................................... 17 5. VIT group options........................................................................................................................................18 6. Deactivating the VIT....................................................................................................................................21 7. VTAM component IDs..................................................................................................................................24 8. Standard Keywords Supported by FFST..................................................................................................... 70 9. Probe Initialization Return Codes...............................................................................................................81 10. Probe Statement Return Codes................................................................................................................ 82 11. Probe Termination Return Codes..............................................................................................................83 12. Dump Return Codes.................................................................................................................................. 92 13. Symptom Record Return Codes................................................................................................................94 14. Generic Alert Return Codes...................................................................................................................... 96 15. Exit-type-dependent information for a UE1 entry................................................................................. 716 16. FFST probe index.................................................................................................................................... 799 17. FFST probe naming conventions............................................................................................................ 800 18. FFST probes for APPN over logical link.................................................................................................. 801 19. FFST probes for APPN TG management................................................................................................ 802 20. FFST probes for CMIP services (ISTCMCxx).......................................................................................... 802 21. FFST probes for configuration services (ISTCSCxx).............................................................................. 802 22. FFST probes for control operator (ISTCOCxx)....................................................................................... 804 23. FFST probes for coupling facility services (ISTFSCxx).......................................................................... 805 vii 24. FFST probes for dependent LU server (ISTDLCxx)................................................................................ 811 25. FFST probes for directory services (ISTDRCxx).....................................................................................812 26. FFST probes for half-session services (ISTHSCxx)................................................................................819 27. FFST probes for Enterprise Extender (ISTAUCxx)..................................................................................819 28. FFST probes for logical link control........................................................................................................820 29. FFST probes for LU network services (ISTNSCxx)................................................................................. 821 30. FFST probes for LU resource manager (ISTRMCxx)...............................................................................821 31. FFST probes for management services transport (ISTMTCxx)..............................................................821 32. FFST probes for network resource management (ISTNACxx).............................................................. 822 33. FFST probes for presentation services (ISTPSCxx)............................................................................... 822 34. FFST probes for recovery manager (ISTRVMxx).................................................................................... 823 35. FFST probes for session services (ISTSSCxx)........................................................................................824 36. FFST probes for session services CP-CP (ISTSCCxx)............................................................................ 824 37. FFST probes for session services LU-LU (ISTSLCxx)............................................................................. 826 38. FFST probes for storage management (ISTORCxx)............................................................................... 833 39. FFST probes for topology and routing services (ISTTRCxx)..................................................................833 40. FFST probes for trace services (ISTRACxx)........................................................................................... 834 41. FFST probes for TC-DLC (ISTTCCxx)...................................................................................................... 834 42. FFST probes for transmission subsystem (ISTTSCxx)...........................................................................835 43. FFST probes for the VTAM topology agent (ISTTACxx)..........................................................................836 44. CSM FFST probe naming conventions....................................................................................................841 45. FFST probes for communications storage manager (IVTSMCxx)..........................................................841 viii About this document This document is intended to help system programmers in a VTAM® environment diagnose problems with the VTAM program. Use the document to isolate and identify problems with your VTAM network and to collect appropriate documentation to resolve network problems. The information in this document includes descriptions of support for both IPv4 and IPv6 networking protocols.
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]
  • 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]
  • 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]
  • Opensource Software Im Alltag
    OpensourceOpensource SoftwareSoftware imim AlltagAlltag -- IstIst dasdas möglich?möglich? Willkommen zum Xing Stammtisch Alexander Demmler – 25.11.2016 © A. Demmler 2016 www.lacunasolutions.com 1 Marktanteile Desktop Systeme 2016 © A. Demmler 2016 www.lacunasolutions.com 2 Webserver Systeme © A. Demmler 2016 www.lacunasolutions.com 3 Einsatz von OSS in US Unternehmen: Northbridge Eine Venture Capital Company. Game changers disrupt existing markets. They also create new multi-billion dollar markets and have the potential to change the way we live and work. http://www.northbridge.com © A. Demmler 2016 www.lacunasolutions.com 4 Was bedeutet OpenSource? • OpenSource Software (OSS) ist professionelle Software unter einer alternativen Entwicklungs- und Vertriebsform • OpenSource ist nicht Linux - aber Linux ist auch OpenSource! • OpenSource bedeutet ein Stück Freiheit: - freie Auswahl - Freiheit ob und wieviel man bezahlt - Freiheit in der Nutzung © A. Demmler 2016 www.lacunasolutions.com 5 Was ist die Community? • Die Community besteht aus - Entwicklern + Beratern + Anwendern + Hobbyisten - grossen Unternehmen (HP, IBM, SUN) - Distributoren wie SUSE, RedHat, Ubuntu u.a. • Die Community entwickelt und pflegt gemeinsam die Software und bietet Unterstützung (Support) • Die Community ist kein Club von Hackern, Freaks und anderen Bösewichten! © A. Demmler 2016 www.lacunasolutions.com 6 Das Geschäftsmodell Freie Software Dienstleistungen (Kosten) Basis Version Erweiterungen Download im WWW Service + Support Online Support Schulungen Zusatzeinkünfte Werbung + Sponsoren © A. Demmler 2016 www.lacunasolutions.com 7 Lizenzrechtliches • Softwarecode (Quellen) sind offen gelegt: - Verbreitung und Nutzung sind ausdrücklich erlaubt - Veränderung (Anpassung, Erweiterung) erlaubt - Quellcode muss offengelegt werden • Es gibt historisch bedingt verschiedene Lizenzmodelle. (GPL, OSL, CPL, EPL u.a) • EU Initiative um Lizenzen vereinen: http://ec.europa.eu ACHTUNG: Auch hier gelten Vorschriften! Computerwoche: http://www.computerwoche.de © A.
    [Show full text]
  • ABC-Klubbens Monitormanual
    Manual för ABC-Klubbens Monitor med programbank och MSG Version 3.44 ABC-Klubben, 1995 ABC-Klubbens Monitor med programbank och MSG Sida 2 ABC-Klubbens Monitor med programbank och MSG Manualen skrevs ursprungligen av J C Liebe-Harkort för gamla ABC-monitorn. Avsnitten om kommunikationsparametrar och filöverföring är skrivna av Bo Kullmar. Avsnitten om monitorns kommandon bygger på Benny Löfgrens hjälptexter i monitorn. Sammanställning och redigering av manualen har gjorts av Bo Kullmar, Per Sten och Johan Persson. Ghlenn Willard har rättat många skrivfel . Pris 50 kronor. ABC-Klubben, 95-7-9 Sida 3 ABC-Klubbens Monitor med programbank och MSG Innehållsförteckning Innehållsförteckning................................................................................................................................ 4 Kapitel 1 - Inledning................................................................................................................................ 7 Inlogging: .................................................................................................................................. 8 Kapitel 2 - Kommunikationsparametrar................................................................................................... 10 Kabel ............................................................................................................................ 10 Modemkablar................................................................................................................ 10 PC ...............................................................................................................................
    [Show full text]
  • Volume 33 — 2001 APRES Proceedings, Oklahoma City, OK
    ............-. -~ _... -..::.._ . .;.:··: -- -~-- -. - --- :_.,_--.. _-· ---~- - .:_~._.c_ --- :..-.... -- '- .-._,_ -.~--·-:-·- -~-- .. ~--- - ·- -- ~·- .. -- - -._-:---:~~.:. _ ___ ... -......... -... ~-·.... ----- -~?FF~ -·-:- -- AMine;~f.Pean~t"Research ·· .and :EdU:Catl~JJ Sociefy;· Jnc. - -- - ~ -- ,:2~. -- ---~:: '· .. -~ ------ '"'•"':.. __ .... _ - .:-----~~~- ~ -=- -- _..... -"-;_..-- - -. - ~· --- ..... -::- ..... -:·-:--. Volume 33 2001 PROCEEDINGS of THE AMERICAN PEANUT RESEARCH AND EDUCATION SOCIETY, INC. Meeting Oklahoma City, Oklahoma July 17-20, 2001 Publication Date March 2002 Editor: J. Ronald Sholar Production Editor: Irene Nickels TABLE OF CONTENTS Board of Directors ........................................................................................ 1 Annual Meeting Sites ................................................................................... 1 APRES Committees ..................................................................................... 2 Past Presidents ............................................................................................ 4 Fellows ......................................................................................................... 4 Bailey Award ................................................................................................ 5 Joe Sugg Graduate Student Award .............................................................. 5 Coyt T. Wilson Distinguished Service Award ................................................ 5 Dow AgroSciences Award for Excellence
    [Show full text]
  • Open Source Used in Staros 21.19
    Open Source Used In StarOS 21.19 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-1023749304 Open Source Used In StarOS 21.191 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-1023749304 Contents 1.1 libxml 2.9.2 1.1.1 Available under license 1.2 acpid 2.0.22 1.2.1 Available under license 1.3 net-snmp 5.1.1 1.3.1 Available under license 1.4 libnuma 2.0.11 1.4.1 Available under license 1.5 popt 1.5 1.5.1 Available under license 1.6 procps 3.2.6 1.6.1 Available under license 1.7 python 2.7.6 1.7.1 Available under license 1.8 openssh 7.6 1.8.1 Available under license 1.9 ftpd-bsd 0.3.2 1.9.1 Available under license 1.10 iconv 2.17 1.10.1 Available under license 1.11 procps 3.2.6 1.11.1 Available under license 1.12 dozer 6.4.1 1.12.1 Available under license 1.13 xmlrpc-c 1.06.38 1.13.1 Available under license Open Source Used In StarOS 21.192 1.14 antlr-runtime 4.2 1.15 kexec-tools 2.0.14 1.15.1 Available under license 1.16 pcre 8.41 1.16.1 Available
    [Show full text]
  • Kermit News March 1995 Brazil: Election Day 1994
    Number 6 Kermit News March 1995 Brazil: Election Day 1994 Brazil's October 1994 general election was almost certainly the world's largest and most complex ever. Kermit software played a crucial role. In Rio de Janeiro, ballots are transcribed to PCs for transmission to the tabulating center by MS-DOS Kermit. Article on page 19. Kermit News Number 6, March 1995 CONTENTS Editor's Notes . 1 New Releases MS-DOS Kermit 3.14 . 3 and BBSs . 4 and Business Communication . 5 C-Kermit 5A(190) . 6 for UNIX . 6 for VMS . 7 for OS/2 . 7 for Stratus VOS . 10 IBM Mainframe Kermit-370 4.3.1 . 11 Digital PDP-11 Kermit-11 3.62-8 . 11 Other New Kermit Releases . 11 New Features File Transfer Recovery . 12 Auto-Upload, Auto-Download, Auto-Anything . 12 Character Sets: Circumnavigating the Web with MS-DOS Kermit . 15 People and Places Cover Story: Kermit in the Brazilian Elections. 19 Kermit Helps Automate Mail Delivery . 23 Kermit and Market Research in the UK . 24 Computer Access for Persons with Print-Handicaps . 25 Down to Business Ordering Information . 28 Kermit Version List . 29 Order Form . 31 Kermit News (ISSN 0899-9309) is published periodically free of charge by Kermit Development and Distribution, Columbia University Academic Information Systems, 612 West 115th Street, New York, NY 10025, USA. Contributed articles are welcome. Editor: Christine M. Gianone E-Mail: cmg@ columbia.edu Copyright 1995, Trustees of Columbia University in the City of New York. Material in Kermit News may be quoted or reproduced in other publications without permis- sion, but with proper attribution.
    [Show full text]
  • Système D'exploitation Compatible Unix Appelé GNU 1987 : Minix Développé Par Tanenbaum 1990 : Debut De Hurd 1991 : Linus Torvals Développe Un Noyaux
    Systèmes d’exploitation mercredi 11 janvier 12 Plan Introduction Interface Différents OS Systèmes de fichiers Mémoire Processus Démarrage Installation Configuration Particularités mercredi 11 janvier 12 Système d’exploitation Propose une interface utilisateur/machine Gestion des ressources materielles Gestion du (des) utilisateur(s) Gestion des processus Sécurité (processus / mémoire) Abstraction -> unification Bibliothèque de fonction Exemples : Windows, MacOS X, Linux, Solaris, *BSD, VMS, Symbian OS ... mercredi 11 janvier 12 Modélisation en couche L’utilisateur demande à l’application L’application demande au noyau Noyau se charge de la base Mémoire ((des)allocation, pas de débordement) CPU (gestion multi-tache, IPC) Gestion des fichiers (hiérarchie) Gestion des périphériques (clavier, souris, vidéo, réseau, etc.) IPC= inter-process communication Appels systèmes (demande de logiciels) mercredi 11 janvier 12 Exemple d’interaction Header lib Header lib API API Module K Application S.E. Interface API = Application Programming Interface mercredi 11 janvier 12 Plan Introduction Interface Différents OS Systèmes de fichiers Mémoire Processus Démarrage Installation Configuration Particularités mercredi 11 janvier 12 Interface Shell Une interface en ligne de commande (CLI) Windows : Command.com / cmd.exe *nix : Bash, ksh, sch, tcsh, zsh, ... Ancien, mais toujours puissante Utilise peu de ressources Ex : Commande arg1 arg2 ... argn La commande qui sauve la vie dans un *nix On écrit dans la doc on écrit les arguments de man <commande> façon suivante : <arg> comme obligatoire [arg] comme optionnel mercredi 11 janvier 12 Interface graphique GUI (Graphical User Interface) User Friendly (ergonomique) Les pictogrammes remplace le text Inventé par Xerox 1973 Alto. Généralement des fenêtres avec une barre de processus. Dirigé avec une sourie ou un écran tactile.
    [Show full text]
  • Lezione? Real-Time Marco Cesati Marco Cesati Lezione R13
    Sistemi operativi Sistemi operativi real-time Di cosa parliamo in questa lezione? real-time Marco Cesati Marco Cesati Lezione R13 Sistemi operativi real-time – II In questa lezione descriviamo brevemente alcuni dei più diffusi Schema della lezione sistemi operativi real-time Schema della lezione Caratteristiche comuni Caratteristiche comuni VxWorks VxWorks LynxOS LynxOS 1 Caratteristiche comuni degli RTOS QNX QNX Sistemi embedded e real-time 2 eCos VxWorks eCos Windows 3 LynxOS Windows Linux come RTOS Linux come RTOS 4 15 gennaio 2013 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 SERT’13 R13.2 Sistemi operativi Sistemi operativi Caratteristiche comuni dei principali RTOS real-time La schedulazione nei principali RTOS real-time Marco Cesati Marco Cesati Corrispondenza agli standard: generalmente le API sono Almeno 32 livelli di priorità differenti proprietarie, ma gli RTOS offrono anche compatibilità Possibilità di scelta fra FIFO e Round Robin per la (compliancy) o conformità (conformancy) allo standard gestione dei task nello stesso livello di priorità Real-Time POSIX Possibilità di cambiare la priorità a run-time Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Schema della lezione Caratteristiche comuni Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili Generalmente non supportano in maniera nativa politiche VxWorks VxWorks di scheduling
    [Show 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......................................................................................................
    [Show full text]