DOCSLIB.ORG

The Transition to the P/390: a User’S Experience

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Transition to the P/390: a User’S Experience INTEROPERABILITY BY MIKE NELSON INSIGHTS The Transition to the P/390: A User’s Experience his article describes my company’s experience installing and using the IBM PC Server 500 System/390, or P/390 as it is called. The ordering and installation of both the T hardware and software was a very different process from that of the traditional MVS hardware and software. This article highlights the experiences of one We ordered the hardware and software system software was not delivered. After company that installed from IBM Direct through the S/390 Partners many phone calls to several 800 numbers, in Development organization (formerly known MVS arrived about two weeks later. the IBM PC Server as the S/390 Developers Association) based Preparing to install the P/390 is not unlike 500 System/390, on a list of features supplied by IBM. This any other system. You must take the time to allowed us to choose the type of hardware, read through the materials supplied. The first and presents some including optional components, as well as the thing you must do is install the PC hardware, operating systems we wanted. We chose if any, and any drivers needed for this hard- guidelines for other MVS/ESA 5.2 as our operating system, but ware. Our only additional hardware was 32 sites contemplating this VM and VSE could have been chosen also. MB of added OS/2 memory. Our P/390 has 64 MB memory for OS/2 The RAID controller diskette must be cre- type of implementation. and 128 MB for MVS. We have divided our ated to configure the disk array. You must use MVS memory into 96 MB for real storage the ServerGuide CD to create the diskettes and 32 MB for expanded storage to help keep needed. See the PC Server 500 User’s MVS paging down. The DASD layout con- Handbook for details on creating the diskettes sists of five 2.25 GB drives for a total of using the ServerGuide. Once the RAID con- 11.25 GB. We chose to use RAID 5 for our figuration diskettes are created, you must disk array subsystem based on a trade-off of decide what RAID configuration you want to data recovery and performance. Using RAID use. We chose the RAID 5 disk array because 5 left us with 9 GB of DASD available for the it has the best mix of performance, capacity, OS/2 and MVS operating systems. At our and recoverability of the RAID configura- site, we have a mixture of both Token-Ring tions. Keep in mind, that with RAID 5, you and Ethernet LANs. All of our “terminals” will lose the capacity of one installed drive. utilize Ethernet, and the Token-Ring is used For example, our disk configuration con- for connection to our 9221 mainframe tained five 2.25 GB disks for a total of 11.25 through a 3720 front-end processor. To allow GB; using the RAID 5 configuration we have us to connect the P/390 into the current system, a total or 9 GB of disk space. This provides us we chose the Auto LANStreamer card. We with automatic recovery in case of a disk opted not to get the optional S/370 channel drive failure. From an MVS/ESA standpoint, emulator. The S/370 channel emulator there is no difference in any of the RAID allows the connection of all S/370 devices via options, because MVS/ESA is not aware that bus/tag connection except for DASD RAID support is being used. (3380/3390). We also have the 4mm DAT Once you have created your RAID con- tape drive and a CD/ROM, which are standard troller diskette from the ServerGuide CD, devices with the P/390. insert this diskette into the primary drive on We placed the order for our P/390 in the P/390 and press Ctrl+Alt+Del to reboot. August 1995, and received it in October, The main menu will appear, and you may which was good response. We encountered proceed with the configuration. One option to one problem, however. The MVS operating keep in mind when configuring the RAID TECHNICAL SUPPORT MARCH 1996 INTEROPERABILITY INSIGHTS Figure 1: VTAM Definition Samples Figure 1: VTAM Definition Samples - continued ATCSTRxx vtamlst member for 9221: P390T005 LU LOCADDR=6 SSCPID=01,NOPROMPT,SSCPNAME=EMPSS,NETID=EMP, X . CONFIG=00,MAXSUBA=15,SUPP=NOSUP, X . NOTRACE,TYPE=VTAM, X TNSTAT,CNSL,TIME=60, X The NCP definitions added for the P/390 connection. This is assuming you already have CSA24=1024, X the NCP genned to support a current Token–Ring connection. IOINT=0, X CRPLBUF=(120,,2,,30,3), X *——— LOGICAL INN CONNECTION FOR P390 ————–––––————————- IOBUF=(88,384,3,F,28,33), X * LPBUF=(24,,2,,1,4), X LATRI102 LINE LOCALTO=2.5, (LN) LOCAL STATION T1 TIMER VALUE * LFBUF=(4,,,,1,1), X REMOTTO=2.5, (LN) REMOTE STATION T1 TIMER VALUE * SPBUF=(04,,,,1,1), X T2TIMER=(0.3,0.3,3), (LN) T2 TIMER VALUE * SFBUF=(100,,,,1,1), X UACB=X$L2A CRPLBUF=(120,,2,,20,3) * PATRI102 PU AD D R = 0 4 4 0 0 0 7 4 9 0 0 0 0 1 , (PN) SAP/LAA OF REMOTE TOKEN-RING * ATCSTRxx vtamlst member for P/390: NETID=EMP, (PN) LINK STATION NETWORK NAME * SSCPID=06,NOPROMPT, X PUTYPE=4, (PN) PHYSICAL UNIT TYPE * CONFIG=00,MAXSUBA=31,SUPP=NOSUP, X TGN=1 (PN) LINK STATIONS TGN * SSCPNAME=P390SS, X With the above definitions added, we needed the ability to move datasets, load libraries, NETID=EMP, X JCL libraries, etc., from our mainframes to the P/390. This is done using standard NJE HOSTSA=6, X definitions for both JES2 and VTAM. Attached are the changes needed for the NJE connection. CRPLBUF=(208,,15,,30,16), X Using the 3720 for the front–end processor requires us to use a 4 MB Token–Ring. This IOBUF=(100,384,19,,28,33), X connection is suprisingly fast when downloading datasets. LFBUF=(104,,0,,1,1), X LPBUF=(64,,0,,1,1), X VTAM definitions on the 9221. SFBUF=(163,,0,,1,1) EMPCDRMS VBUILD TYPE=CDRM Since the AWS3172 device driver emulates a 3172, you must have at least one UCB genned as a CTC EMPSS CDRM SUBAREA=1,CDRDYN=YES,CDRSC=OPT (3088). Once this is done, you can set up the VTAM definitions that define the 3172 connection. P390SS CDRM SUBAREA=6,CDRDYN=YES,CDRSC=OPT * * 3172 LAN CONNECTION N15CYADJ VBUILD TYPE=ADJSSCP * P390SS ADJCDRM LANTRXCA VBUILD TYPE=XCA XCA MAJOR NODE VTAMA ADJCDRM PORT1 PORT MEDIUM=RING, TOKEN RING LAN X SAPADDR=4, SERVICE ADDRESS POINT ADDRESS X ***************************************************************** ** ADAPNO=0, ADAPTER NUMBER X * PATH DEFINITIONS TO 3720 * CUADDR=E20 CHANNEL UNIT ADDRESS ***************************************************************** ** * PATH DESTSA=(15), C * XCA MAJOR NODE FOR TOKEN RING ER0=(15,1), C * ER1=(15,1), C GROUP1 GROUP ANSWER=ON, DIAL WILL ACCEPT CALLS X ER6=(15,1), C CALL=INOUT, DIAL ON AND OUT X VR0=0, C DIAL=YES, SWITCHED NODE (PERIPHIAL CONNECT) X VR1=1, C ISTATUS=ACTIVE ACTIVATE AT GEN VR6=6 LINE1TA LINE ***************************************************************** ** PU1TA PU * PATH DEFINITIONS TO P390 * GROUP2 GROUP DIAL=NO, NO SWITCED LINE (SUBAREA CONNECT) X ***************************************************************** ** ISTATUS=ACTIVE ACTIVATE AT GEN PATH DESTSA=(6), C LINE2TA LINE ER0=(15,1), C PU2TA PU MACADDR=400045210101, ADDR OF 3720 TOKEN RING X ER1=(15,1), C PUTYPE=4, X VR0=0, C SAPADDR=04, X VR1=1 SUBAREA=15, NCP SUBAREA ID X TGN=1 EMPNJE VBUILD TYPE=APPL EMPNJE1 APPL ACBNAME=EMPNJE1,EAS=4,AUTH=(PASS,ACQ,VPACE), X The VTAM Switched major node must be defined if one does not exist. VPACING=4,MODETAB=MODETEMP,DLOGMOD=JES2NJE * * SWITCHED MAJOR FOR TOKEN RING 3172 VTAM defintions on the P/390 * P390SWI VBUILD TYPE=SWNET,MAXGRP=32,MAXNO=32 EMPCDRMS VBUILD TYPE=CDRM * EMPSS CDRM SUBAREA=1,CDRDYN=YES,CDRSC=OPT P390SPU1 PU ADDR=01, X P390SS CDRM SUBAREA=6,CDRDYN=YES,CDRSC=OPT ANS=CONT, X CPNAME=P390SWT, X * DLOGMOD=EMC32792, X PATH DESTSA=(15), C IDBLK=05D, X ER0=(15,1), C IDNUM=00001, X ER1=(15,1), C IRETRY=YES, X ER6=(15,1), C ISTATUS=ACTIVE, X VR0=0, C MAXDATA=1024, VR1=1, C MAXOUT=7, X VR6=6 MAXPATH=4, X * MODETAB=MODETEMP, X PATH DESTSA=(1), C PASSLIM=5, X ER0=(15,1), C PUTYPE=2, X ER1=(15,1), C USSTAB=USSEMPS VR0=0, C P390PTH1 PATH DIALNO=0004400074900001, TIC(2)/SAP(2)/MACADDR X VR1=1 GRPNM=GROUP1 * NJEP390 VBUILD TYPE=APPL P390NJE APPL ACBNAME=P390NJE,EAS=4,AUTH=(PASS,ACQ,VPACE), X P390T001 LU LOCADDR=2 VPACING=4,MODETAB=MODETEMP,DLOGMOD=JES2NJE P390T002 LU LOCADDR=3 P390T003 LU LOCADDR=4 Also, you may need to create a Class of Service table on each machine (ISTSDCOS). P390T004 LU LOCADDR=5 INTEROPERABILITY INSIGHTS Figure 2: JES2 Definitions of the choices require some advanced planning. Make sure you use the CD-ROM version of OS/2 Warp shipped with the PC Server S/390 The JES2 definitions added to the 9221. and not the one shipped with the ServerGuide. During the OS/2 Warp APPL(P390NJE) NODE=x installation, we created a 200 MB FAT partition for OS/2 and other - - - - - - - - programs. The rest of the drives we configured as an HPFS partition CONNECT NODEA=1, for P/390 programs and emulated 3380s, etc. MEMBERA=1, NODEB=x, MVS/ESA also requires Communications Manager/2 (CM/2) to be MEMBERB=1, installed. CM/2 allows the PC Server System/390 to use the OS/2 PATHMGR=NO, video to emulate a local non-SNA 3270 device, which will be used as REST=2 the MVS master console.You need to use CM/2 Version 1.11 shipped - - - - - - - - LINE(x) UNIT=SNA with the P/390 rather than the ServerGuide.
Load more

Recommended publications
  • The Operating System Handbook Or, Fake Your Way Through Minis and Mainframes
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme MVS Table of Contents Chapter 22 MVS: An Introduction.................................................................................... 22.1 Batch Jobs..................................................................................................................1 22.2 Interacting with MVS................................................................................................3 22.2.1 TSO.........................................................................................................................3 22.2.2 ISPF........................................................................................................................3 22.2.3 CICS........................................................................................................................4 22.2.4 Other MVS Components.........................................................................................4 22.3 History........................................................................................................................5 Chapter 23 Getting Started with MVS............................................................................... 23.1 Starting Up.................................................................................................................6 23.1.1 VTAM.....................................................................................................................6 23.1.2 Logging On.............................................................................................................6
    [Show full text]
  • PKZIP MVS User's Guide
    PKZIP for MVS MVS/ESA, OS/390, & z/OS User’s Guide PKMU-V5R5000 PKWARE, Inc. PKWARE, Inc. 9009 Springboro Pike Miamisburg, Ohio 45342 Sales: 937-847-2374 Support: 937-847-2687 Fax: 937-847-2375 Web Site: http://www.pkzip.com Sales - E-Mail: [email protected] Support - http://www.pkzip.com/support 5.5 Edition (2003) PKZIP for MVS™, PKZIP for OS/400™, PKZIP for VSE™, PKZIP for UNIX™, and PKZIP for Windows™ are just a few of the many members in the PKZIP® family. PKWARE, Inc. would like to thank all the individuals and companies -- including our customers, resellers, distributors, and technology partners -- who have helped make PKZIP® the industry standard for Trusted ZIP solutions. PKZIP® enables our customers to efficiently and securely transmit and store information across systems of all sizes, ranging from desktops to mainframes. This edition applies to the following PKWARE of Ohio, Inc. licensed program: PKZIP for MVS™ (Version 5, Release 5, 2003) PKZIP(R) is a registered trademark of PKWARE(R) Inc. Other product names mentioned in this manual may be a trademark or registered trademarks of their respective companies and are hereby acknowledged. Any reference to licensed programs or other material, belonging to any company, is not intended to state or imply that such programs or material are available or may be used. The copyright in this work is owned by PKWARE of Ohio, Inc., and the document is issued in confidence for the purpose only for which it is supplied. It must not be reproduced in whole or in part or used for tendering purposes except under an agreement or with the consent in writing of PKWARE of Ohio, Inc., and then only on condition that this notice is included in any such reproduction.
    [Show full text]
  • Download for Z/OS
    Print Services Facility for z/OS Version 4, Release 6.0 Download for z/OS IBM S550-0429-05 Note Before using this information and the product it supports, read the information in “Notices” on page 83. This edition applies to the IBM® Print Services Facility™ Version 4 Release 6 Modification 0 for z/OS®, Program Number 5655-M32, and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces S550-0429-04. © Copyright International Business Machines Corporation 1995, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures...................................................................................................... vii List of Tables........................................................................................................ ix About this publication...........................................................................................xi Who should read this publication............................................................................................................... xi How this publication is organized............................................................................................................... xi Understanding the syntax notation used in this publication......................................................................xi Related information....................................................................................................................................xii
    [Show full text]
  • Airline Control System Version 2: General Information Manual Figures
    Airline Control System Version 2 IBM General Information Manual Release 4.1 GH19-6738-13 Airline Control System Version 2 IBM General Information Manual Release 4.1 GH19-6738-13 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page ix. This edition applies to Release 4, Modification Level 1, of Airline Control System Version 2, Program Number 5695-068, and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. A form for readers’ comments appears at the back of this publication. If the form has been removed, address your comments to: ALCS Development 2455 South Road P923 Poughkeepsie NY 12601-5400 USA When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corporation 2003, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures .................................... v Tables .................................... vii Notices .................................... ix Trademarks ................................... ix About this book ................................ xi Who should read this book .............................. xi Related publications ...............................
    [Show full text]
  • Z/OS ♦ Z Machines Hardware ♦ Numbers and Numeric Terms ♦ the Road to Z/OS ♦ Z/OS.E ♦ Z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services
    Mainframes The Future of Mainframes Is Now ♦ z/Architecture ♦ z/OS ♦ z Machines Hardware ♦ Numbers and Numeric Terms ♦ The Road to z/OS ♦ z/OS.e ♦ z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services by Steve Comstock The Trainer’s Friend, Inc. http://www.trainersfriend.com 800-993-8716 [email protected] Copyright © 2002 by Steven H. Comstock 1 Mainframes z/Architecture z/Architecture ❐ The IBM 64-bit mainframe has been named "z/Architecture" to contrast it to earlier mainframe hardware architectures ♦ S/360 ♦ S/370 ♦ 370-XA ♦ ESA/370 ♦ ESA/390 ❐ Although there is a clear continuity, z/Architecture also brings significant changes... ♦ 64-bit General Purpose Registers - so 64-bit integers and 64-bit addresses ♦ 64-bit Control Registers ♦ 128-bit PSW ♦ Tri-modal addressing (24-bit, 31-bit, 64-bit) ♦ Over 140 new instructions, including instructions to work with ASCII and UNICODE strings Copyright © 2002 by Steven H. Comstock 2 z/Architecture z/OS ❐ Although several operating systems can run on z/Architecture machines, z/OS is the premier, target OS ❐ z/OS is the successor to OS/390 ♦ The last release of OS/390 was V2R10, available 9/2000 ♦ The first release of z/OS was V1R1, available 3/2001 ❐ z/OS can also run on G5/G6 and MP3000 series machines ♦ But only in 31-bit or 24-bit mode ❐ Note these terms: ♦ The Line - the 16MiB address limit of MVS ♦ The Bar - the 2GiB limit of OS/390 ❐ For some perspective, realize that 16EiB is... ♦ 8 billion times 2GiB ♦ 1 trillion times 16MiB ❐ The current release of z/OS is V1R4; V1R5 is scheduled for 1Q2004 Copyright © 2002 by Steven H.
    [Show full text]
  • Microkernel Vs
    1 VIRTUALIZATION: IBM VM/370 AND XEN CS6410 Hakim Weatherspoon IBM VM/370 Robert Jay Creasy (1939-2005) Project leader of the first full virtualization hypervisor: IBM CP-40, a core component in the VM system The first VM system: VM/370 Virtual Machine: Origin 3 IBM CP/CMS CP-40 CP-67 VM/370 Why Virtualize 4 Underutilized machines Easier to debug and monitor OS Portability Isolation The cloud (e.g. Amazon EC2, Google Compute Engine, Microsoft Azure) IBM VM/370 Specialized Conversation Mainstream VM al Monitor OS (MVS, Another Virtual subsystem System DOS/VSE copy of VM machines (RSCS, RACF, (CMS) etc.) GCS) Hypervisor Control Program (CP) Hardware System/370 IBM VM/370 Technology: trap-and-emulate Problem Application Privileged Kernel Trap Emulate CP Classic Virtual Machine Monitor (VMM) 7 Virtualization: rejuvenation 1960’s: first track of virtualization Time and resource sharing on expensive mainframes IBM VM/370 Late 1970’s and early 1980’s: became unpopular Cheap hardware and multiprocessing OS Late 1990’s: became popular again Wide variety of OS and hardware configurations VMWare Since 2000: hot and important Cloud computing Docker containers Full Virtualization 9 Complete simulation of underlying hardware Unmodified guest OS Trap and simulate privileged instruction Was not supported by x86 (Not true anymore, Intel VT-x) Guest OS can’t see real resources Paravirtualization 10 Similar but not identical to hardware Modifications to guest OS Hypercall Guest OS registers handlers Improved performance VMware ESX Server 11 Full virtualization Dynamically rewrite privileged instructions Ballooning Content-based page sharing Denali 12 Paravirtualization 1000s of VMs Security & performance isolation Did not support mainstream OSes VM uses single-user single address space 13 Xen and the Art of Virtualization Xen 14 University of Cambridge, MS Research Cambridge XenSource, Inc.
    [Show full text]
  • Floboss 107 Flow Manager Instruction Manual
    Part Number D301232X012 May 2018 FloBoss™ 107 Flow Manager Instruction Manual Remote Automation Solutions FloBoss 107 Flow Manager Instruction Manual System Training A well-trained workforce is critical to the success of your operation. Knowing how to correctly install, configure, program, calibrate, and trouble-shoot your Emerson equipment provides your engineers and technicians with the skills and confidence to optimize your investment. Remote Automation Solutions offers a variety of ways for your personnel to acquire essential system expertise. Our full-time professional instructors can conduct classroom training at several of our corporate offices, at your site, or even at your regional Emerson office. You can also receive the same quality training via our live, interactive Emerson Virtual Classroom and save on travel costs. For our complete schedule and further information, contact the Remote Automation Solutions Training Department at 800-338-8158 or email us at [email protected]. ii Revised May-2018 FloBoss 107 Flow Manager Instruction Manual Contents Chapter 1 – General Information 1-1 1.1 Scope of Manual ............................................................................................................................1-2 1.2 FloBoss 107 Overview ...................................................................................................................1-2 1.3 Hardware ........................................................................................................................................1-5
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • Specifications
    Specifications SYSTEM PERFORMANCE Standard & Advanced Editions Advanced Edition Only 96-Well Verification Plate 384-Well Verification Plate Time Requirements < 5 minutes < 10 minutes Tip Configurations 1, 2, 4, 6, 8, 12, and 96 1, 8, 12, 16, 24, 96, and 384 Traceable Volume Range 0.1000 - 350.0 µL 0.0100 - 55.00 µL Operating Volume Range* 0.0001 - 350.0 µL 0.0001 - 55.00 µL Artel 800TSNB Plate Reader Uncertainty (Inaccuracy)** 0.2000 - 350.0 µL, ± 2.0% 0.0500 - 55.00 µL, ± 2.5% 0.1000 - 0.1999 µL, ± 3.0% 0.0200 - 0.0499 µL, ± 3.5% 0.0100 - 0.0199 µL, ± 5.5% Random Error (Imprecision)** 0.2000 - 350.0 µL, ≤ 0.4% 0.0500 - 55.00 µL, ≤ 0.8% 0.1000 - 0.1999 µL, ≤ 0.4% 0.0200 - 0.0499 µL, ≤ 0.8% 0.0100 - 0.0199 µL, ≤ 0.9% Operating Temperature for Aqueous Sample Solutions 15 - 30 °C 15 - 30 °C Operating Temperature for DMSO Sample Solutions 19 - 30 °C 19 - 30 °C Traceability to national & international standards using Yes Yes Artel MVS Verification Plates PERFORMANCE SPECIFICATION DEFINITIONS • When each well in an MVS Verification Plate is uniformly1 filled with a known2 volume of MVS Sample Solution and measured with an Artel MVS Plate Reader, each individual well measurement will be within the stated MVS inaccuracy specification at a statistical confidence of 95% or better.3 • The CV across the full plate (96 or 384 individual results) will also be within the stated imprecision specification at a statistical confidence of 95% or better.4 1.
    [Show full text]
  • VM/SP Introduction.Pdf
    GC19-6200-1 File No. S370/4300-20 Program Product GC19-6200-1 File No. S370/4300-20 IBM Virtual Machine/ System Product: Program Product Introduction Program Number 5664-167 Release 2 -----~- - i::~~ Second Edition (April 1982) This edition, GC19-6200-1, is a reV1S10n of GC19-6200-0. It applies to the IBft Virtual ~achine/System Product (5664-167) until otherwise indicated in new editions or ~echnical Newsletters. Changes are continually made to the information contained herein; before using this publication in connection with the operaticn of IBft systems, consult the IB~ 2:i2tem/370 and .!!300 f!:~.§§£!§ Bibli.£g~, GC20-0001, for the editions that are applicable and current. For a list of changes, see page iii. Technical changes or additions to the text cr illustrations are indicated by a vertical bar to the left of the change. It is possible that this material may contain reference to, or information about, IB~ products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that lEft intends to announce such IB~ products, programming, or services in your country. Publications are not stocked at the address given below; requests for IB~ publications should be made to your IBft representative or to the IB~ branch office serving your locality. A form for reader's comments is provided at the back of this publication. If the torm has been removed, comments may be addressed to IB~ Corporation, Programming Publications, Department G60, P.O. Box 6, Endicott, New York, U.S.A.
    [Show full text]
  • Z/OS Basics: Virtual Storage Management (VSM) Overview
    IBM Systems & Technolgy Group z/OS Basics: Virtual Storage Management (VSM) Overview Elpida Tzortzatos – email: [email protected] © 2009 IBM Corporation 1 AgendaAgenda z/OSz/OS Memory/StorageMemory/Storage TypesTypes z/OSz/OS MemoryMemory ManagersManagers 3131--BitBit VSMVSM Basics Recent Enhancements 6464--BitBit VSM/RSMVSM/RSM Basics Recent Enhancements AppendicesAppendices CSA Common Storage Tracker 2 z/OSz/OS Memory/StorageMemory/Storage TypesTypes 3 z/OSz/OS MemoryMemory TypesTypes MemoryMemory managementmanagement viewsviews Page Datasets Auxiliary slots on Virtual pages in Real storage (DASD) volumes multiple address spaces frames (physical (paging datasets) CPU memory) (created through DAT) 4 z/OSz/OS MemoryMemory ControlsControls RealReal Mixture of z/OS internal thresholds and system-wide parameters VirtualVirtual Customer -specified policies via JCL, System Management Facility (SMF) parameters and exits Generally either prevent work exceeding the limits from starting or causes work to terminate if it exceeds a limit during execution Process -level granularity AuxAux z/OS internal thresholds coupled with paging dataset configuration: number of datasets, size of each 5 Storage Types (all with respect to z/OS ’s point of view) Virtual memory/storage DAT -on addressing Explicitly allocated either by the system or applications 24, 31, or 64 bit residency mode ( rmode ) 31 -bit virtual is allocated/freed in multiple of 8 byte chunks 64 -bit virtual is allocated in 1MB multiples on a 1M boundary Virtual storage
    [Show full text]
  • CA OPS/MVS Event Management and Automation Product Brief
    Product Brief CA OPS/MVS® Event Management and Automation At a Glance CA OPS/MVS® Event Management and Automation (CA OPS/MVS) gives Key Benefits/Results organizations the ability to simplify mainframe management through • Improves availability of your z/OS policy-based automated policies and the flexibility to implement business- environment, aligns IT to business specific processes. Designed to manage the availability of critical z/ needs and helps manage IT costs OS resources, the solution helps maintain optimal mainframe system • Increases operational efficiencies and conditions by managing daily operations according to defined business reduces TCO through synchronous policies, replacing the need to manually react to console messages and automation of processes write-to-operator messages. CA OPS/MVS proactively monitors and manages started tasks, online applications, subsystems, JES initiators, and • Centralizes and simplifies system management, helping to optimize other z/OS resources. the resources in your mainframe environment Business Challenge • Centralized visibility of automation Today’s dynamic z/OS environment produces literally thousands of event scripts across the entire mainframe messages every day, some critical and some merely noise. To ensure that environment the red-flag messages (those that can impact service level agreements, business processing, and performance of system resources) receive priority Key Features status, enterprises need an advanced automation and management tool • System State Manager: Provides that is available on demand, 24x7. policy-based, cross-system resource management, implementing • TCO: Customers are looking to maximize the cost reduction in their dependencies, high availability, and IT environments by working with systems that provide value across recovery. platforms and maximize efficiency of users and resources.
    [Show full text]