5749-010 - VIRTUAL MACHINE FACILITY/370 (VM/370)


Table of Contents

5749-010 - VIRTUAL MACHINE FACILITY/370 (VM/370)
NO LONGER AVAILABLE AS OF APRIL 24, 1989.
ABSTRACT
DESCRIPTION
VM/370 HIGHLIGHTS
RELEASE 6 HIGHLIGHTS
RELEASE 5 HIGHLIGHTS
AP HIGHLIGHTS
HIGHLIGHTS OF RELEASE 4
RELEASE 3 PLC 8 HIGHLIGHTS
HIGHLIGHTS OF RELEASE 3
OPTIMIZING VIRTUAL MACHINE PERFORMANCE
INTEGRATED EMULATORS UNDER VM/370
PROGRAMS SUPPORTED IN VM/370 VIRTUAL MACHINES
CUSTOMER RESPONSIBILITIES
COMPATIBILITY STATEMENT FOR CP-67/CMS USERS
SPECIFIED OPERATING ENVIRONMENT
TELECOMMUNICATIONS SUPPORT SUMMARY
RPQ AVAILABILITY
TERMINALS SUPPORTED AS VIRTUAL MACHINE OPERATOR CONSOLES
TERMINALS SUPPORTED FOR REMOTE SPOOLING
TRANSMISSION CONTROL UNITS SUPPORTED BY VM/370
CONFIGURATIONS SUPPORTED BY CMS
MINIMUM VM/370 CONFIGURATION
REPRESENTATIVE VM/370 CONFIGURATION
CUSTOMER ENGINEERING CONSIDERATIONS
RELIABILITY, AVAILABILITY AND SERVICEABILITY
SECURITY AND AUDITABILITY
PERFORMANCE
INSTALLATION PLANNING
PROGRAMMING UPDATE SERVICE
PUBLICATIONS
SCP PROGRAMMING SERVICES: Class 1 SCP

5749-010 - VIRTUAL MACHINE FACILITY/370 (VM/370)


NO LONGER AVAILABLE AS OF APRIL 24, 1989.

Possible Product Replacement is VM/SP.


ABSTRACT

Virtual Machine Facility/370, a multiple-access system for S/370 mdls 135, 135-3, 138, 145, 145-3, 148, 155II, 158, 158AP, 165II, 168, 168AP, the 3031, 3031AP, 3032, 3033, 4321, 4331, 4341 and 4361 Processors contains four major elements:

  1. A control program, CP, which controls the resources of the real computer to provide multiple virtual machines. Each virtual machine can run a different operating system such as OS(/VS), DOS(/VS), CMS, and RSCS and can provide virtual storage support for operating systems that do not offer such support.

  2. The Conversational Monitor System, CMS, a component that gives users a wide range of conversational facilities including creation and management of files and compilation, testing, and execution of problem programs.

  3. The Remote Spooling Communications Subsystem, RSCS, a component that enables users to transmit files to and receive files from remote stations in the RSCS teleprocessing network.

  4. The Interactive Problem Control System, IPCS, a component that enhances the support of VM/370 by providing interactive online facilities for problem management, problem determination and problem isolation. VM/370 also supports the S/370 mdls 158AP, 168AP, 3031AP and 3033AP. S/370 mdls 158MP, 168MP, 4321, 4331 and 4341 are also supported but only when running in uniprocessor mode or with an asymmetric I/O configuration. In an asymmetric I/O configuration, all I/O attached to the system must be attached to one processor. Operation of VM/SP on a 4321 processor is recommended in a VM/CMS-only environment.

DESCRIPTION

The Virtual Machine

The control program (CP) of VM/370 manages the resources of a S/370 to provide virtual storage support through the implementation of virtual machines.

Each virtual machine user appears to have the functional capabilities of a dedicated S/370 available. The remote terminal acts as the virtual systems console for the virtual machine. Other users may be running batch, teleprocessing, testing or time sharing jobs at the same time.

Each user can specify the configuration required: the number, type and I/O addresses of all devices to be used, and from 8,192 bytes to 16 million bytes of storage, provided sufficient resources are available with the real machine's configuration.

Virtual devices, excepting virtual channel-to-channel adapters, must have real counterparts. For example, many users' virtual readers, punches and printers can be 'mapped' or redirected onto common spool disks. VM/370 allows a physical disk pack to be logically subdivided into many separate minidisks, or virtual disks, each with its own virtual I/O address and each encompassing a user-determined number of contiguous cylinders. The use of virtual disks significantly expands the number of different users or operating systems that can have concurrent access to direct access storage devices, and may improve the utilization of available disk space without compromising the integrity of any user's data stored on the disk.

Each user's virtual computer comprises a processor operator's console (the user's remote terminal), a virtual Processor with or without Dynamic Address Translation, a virtual storage size ranging from 8,192 bytes to 16 million bytes, and virtual I/O channels and I/O devices. Virtual machine configurations may also include transmission control units and channel-to-channel adapters. Virtual I/O devices are logically controlled by the virtual machine's operating system and not by VM/370, with the exception of those virtual unit-record devices that are spooled by VM/370 to/from disk. The basic device support for the proper number and type of I/O devices must be generated into the operating system's supervisor or nucleus.

The following operating systems can execute in VM/370 virtual machines: DOS, DOS/VS, OS/PCP, OS/MFT, OS/MVT, OS/VS1, OS/VS2, OS-TSO, OS-ASP, PS44, RSCS, APL/DOS-360 (with CP option), VM/370 and CMS. The control program intercepts, translates and schedules all real I/O operations of the virtual machine. All virtual machines execute in problem state, and the control program intercepts and processes all interrupts and privileged instructions. Only the control program executes in the supervisor state.

The user can select various versions and levels of IBM operating systems, including OS/VS, DOS/VS, OS and DOS, to run in the virtual machine, subject to the following major restrictions:

  • Machine or program timing dependencies may not exist. (That is, there is no reliance on a certain action or activity being completed within a fixed interval of time.)

  • The DIAGNOSE instruction may not be used for machine control by an operating system running in a VM/370 virtual machine. Use of the DIAGNOSE instruction for communication with VM/370 is permitted and recommended. See "VM/370: System Programmer's Guide" (GC20-1807).

  • The READ DIRECT and WRITE DIRECT instructions may not be used in a VM/370 virtual machine.

  • No dynamic modification of channel programs is permitted except within a virtual = real machine or when performed by either the OS Indexed Sequential Access Method (ISAM), OS/VS1 BTAM Autopoll, or the OS/VS Telecommunications Access Method (TCAM) Level 5 and above. (A dynamically modified channel program is one that is changed by the processor or the channel during the interval between the execution of the START I/O instruction and the channel end interrupt.)

  • VM/370 supports OS/VS TCAM Level 5 and above in a virtual environment. This support is intended for use by TCAM applications in a testing environment and is not recommended for production systems. When attempting to identify problems which are encountered when using TCAM under VM/370, it may be advantageous to recreate the problem in a stand-alone OS/VS1 or OS/VS2 environment.

  • DOS Emulation under OS in a virtual machine is not supported. VM/370 provides its own method of running DOS and OS systems concurrently.

  • OS/VS2 must run in uniprocessor mode.

    For a comprehensive list of restrictions, see the "IBM Virtual Machine Facility/370: Planning and System Generation Guide" (GC20-1801).

The Control Program

The control program (CP) of VM/370 creates and controls virtual machines, multiprogramming the resources of the real computer to offer concurrent execution of multiple virtual machines. Local and remote terminals on the real computing system are controlled either by CP as virtual system consoles or by a multiple-access operating system executing in a virtual machine (e.g., RSCS).

All virtual machines execute in problem state, providing the basic mechanism for control by permitting either CP or the Virtual Machine Assist hardware feature to trap and process all interrupts and privileged instructions. Extended Control-Program Support for VM/370 is an expansion of Virtual Machine Assist to further reduce the real supervisor state time used by VM/370 while performing its control functions. The reduction in VM/370 supervisor state time is accomplished in three ways:

  1. Certain privileged instructions are emulated by the hardware rather than simulated by the software.

  2. A hardware assist has been implemented for VM/370 that is designed to be executed only by VM/370.

  3. Extended Control-Program Support for VM/370 also includes support of an interval timer in a virtual machine. The heavily used portions of CP are kept in main storage. All portions of CP execute in supervisor state with Dynamic Address Translation off.

Execution under VM/370 does not require communication between CP and the virtual machine operating system since, subject to the restrictions listed above, the virtual machine interface is that of the real machine. Communication is available however through use of the Diagnose interface: CMS utilizes the DIAGNOSE instruction for many operations including I/O operations; and VS1 Release 4 and above utilizes it to support VM/VS Handshaking.

Time Management

CP periodically gives each virtual machine access to the real processor for a small amount of time, called a 'time slice'. To determine how frequently and for how much time a virtual machine should gain access to the real processor, CP examines the number of console requests or terminal interrupts the virtual machine has issued during its past time slices. If these were many, CP defines the virtual machine as a conversational user and assigns it the smaller of two possible time slices. If they were few, the virtual machine is considered a non-conversational user and is assigned the larger time slice. CP gives conversational users more frequent access to the processor, and the major objective of its algorithms is to provide interactive users with the best possible response times.

Storage Management

Each virtual machine's storage is created and controlled by CP as virtual storage and is organized into 4K blocks called pages and 64K blocks called segments. For each virtual machine, CP creates and maintains a set of segment and page tables to describe the virtual storage and to reflect the allocation in real storage. In addition CP creates a set of shadow page tables for each virtual machine that creates and controls virtual storage of its own.

The active pages from all logged-on virtual machines and from the pageable routines of CP compete for available page frames. When the number of page frames available for allocation falls below a threshold value, CP determines which virtual storage pages currently allocated to real storage are relatively inactive and initiates suitable page-out operations to disk for them. Paging is done on demand, thus a page-in operation does not occur until a page is referenced during virtual machine execution.

One or more virtual storage segments can be read-shared among virtual machines. The information to be shared must be part of an operating system (e.g., CMS) that does not create or control virtual storage and that has been recorded ('saved') in page-format on a VM/370 system disk. These segments can be outside the address spaces of the virtual machines.

Virtual I/O Management

Because virtual machines execute in problem state, CP gains control whenever a START I/O instruction is issued by a virtual machine operating system. CP copies into its own work area the channel command list and pages into real storage all virtual storage locations required for data transfer. If a virtual device is a minidisk, any cylinder numbers specified are modified to reflect the true location of the data; the virtual device address is mapped to the real device address. The virtual machine is given a suitable condition code to indicate the status of the START I/O operation, and CP reflects the interrupts caused by the I/O operation to the virtual machine enabling it to initiate any required error recovery operations.

Since a virtual disk device (full disk or minidisk) may be shared among multiple virtual machines and a particular virtual machine may have read-only or read/write access to a shared disk, CP verifies each virtual machine I/O operation against parameters in the virtual machine's configuration to ensure device integrity.

Spooling

CP spooling facilities allow multiple virtual machines to share unit record devices by intercepting and modifying the Start I/O operations to those virtual unit record devices designated as spooled in the virtual machine configuration. CP uses its paging I/O mechanism to create the disk records which act as intermediate storage between the real unit record devices and the virtual machines.

The spooling facilities allow data files to be transferred between virtual machines or between different operating systems executing at different times in the same virtual machine. In addition, virtual machine console input/output data may be spooled to disk for later printing.

CP Commands

CP commands allow control of the real computing system and VM/370 and provide user control of virtual machines and associated CP facilities. CP commands can be used at any time without regard to which operating system is executing in the virtual machine. A user's privilege class(es), defined as part of his virtual machine configuration, defines his allowable subset of CP commands.

The Conversational Monitor System

A generalized conversational facility for interactive program development, problem solving and end-user applications is offered by the Conversational Monitor System (CMS) component of VM/370.

The CMS command language provides each user with a wide range of capabilities at his remote terminal, such as:

  • Creating source programs, data and text files directly on disk.

  • Adding, deleting, modifying, rearranging, extracting or merging files and/or portions of files.

  • Compiling, testing and debugging some types of OS, DOS problem programs under CMS. These tasks can also be performed for CMS problem programs as well. Languages supported under CMS include the latest levels of COBOL, PL/I, FORTRAN, BASIC, APL and Assembler.

  • Creating complete job streams to be passed to batch operating systems such as DOS or OS for compilation and/or execution. The resultant output can be printed on a high-speed printer or directed back to CMS for analysis and correction by the user.

  • Submitting high-resource jobs to a background CMS Batch Facility for serial execution.

  • Extending CMS facilities to suit his own requirements, e.g., creating additional commands from his own programs or developing command procedures as CMS EXEC files.

CMS allows a programmer to increase his productivity by reducing or eliminating requirements for JCL preparation and by permitting the user to assemble and test whenever he wants, as often as he desires, and for as long as he needs, provided that sufficient I/O devices are available. A programmer can concentrate his efforts on one project at a time, completing projects faster, and putting applications into productive use sooner. The VM/370 data security and user-isolation features protect other users from his errors, and, likewise, protect his data, programs, and disk files from access or destruction by others.

CMS is a single task system designed specifically for the virtual machine environment of VM/370. Each CMS user executes in his own virtual machine. User programs and CMS commands executing under CMS communicate with the user via I/O to the virtual operator's console. Programs coded using CMS macros or certain OS or DOS macros will execute under CMS with restrictions in the following major areas:

  • ISAM
  • Multitasking
  • TP access methods
  • Overlay program structures
  • Other I/O-related restrictions

For more detailed information about the execution-time restrictions of assembler language programs under CMS, refer to the publication "IBM VM/370: System Programmer's Guide" (GC20-1807). Refer to the section "IBM Program Product Support for VM/370" for additional information on the Compiler Program Products supported under CMS.

The CMS file system utilizes chained, fixed-length blocks that are allocated and deallocated automatically as required by the logical file size. Programs executing under CMS can read and write these CMS files via CMS I/O macros, OS BSAM, QSAM or BDAM macros, or DOS sequential I/O macros. CMS files are identified by a three part designator consisting of filename, filetype and filemode; filename and filetype are self-explanatory, and filemode describes the location and access mode of the file. CMS files may be read and written only by programs executing under CMS.

CMS offers the capability of reading, but not writing or updating, OS sequential and partitioned data sets using the CMS MOVEFILE command and OS QSAM, BPAM, and BSAM macros. Under CMS, users can also read DOS SAM data files using the same commands and macros used for reading OS data sets as well as the DOS sequential I/O macros. To provide data portability and compatibility between CMS, OS and DOS, CMS supports read, update and write access to VSAM data sets from COBOL, PL/I, and VS BASIC programs.

VM/370 Assembler

The language of the VM/370 Assembler is the same as the language of the OS/VS Assembler. Four system macro libraries are distributed and contain CMS macros as well as OS Release 20.6 macros. The language of the DOS/VS Assembler is a subset of the language supported by the VM/370 Assembler. Assembler language programs written using DOS/VS macro instructions may be processed by the VM/370 Assembler if the user-installation has created a CMS library containing a copy of the DOS/VS macros found in the DOS/VS source statement library. However, no option is available to flag uses of the extended features of the language which are supported by the VM/370 Assembler but not by the DOS/VS Assembler.

Remote Spooling Communications Subsystem - RSCS

VM/370 remote spooling support is provided for the general user in the form of the Remote Spooling Communications Subsystem (RSCS) component. RSCS, using the existing VM/370 spool file system, allows spooling of data between any virtual machine and 2770, 2780, 3770 (except 3777-2) as a 2770; 3776 and 3777-1 also as a 3780, and 3780 terminals as well as 8100/DPPX running DPPX/RJE (BSC) or 8100/DPPX/SP running DPPX/SP/RJE (BSC) and HASP supported workstations and main processors running HASP, ASP, RES, JES2 and JES3.

RSCS is a multitasking supervisor supporting multiple, concurrent remote spooling operations while running in a single VM/370 virtual machine. It is designed so that a separate task supports the specific device characteristics of each remote terminal or workstation attached to the virtual machine via a teleprocessing line. The RSCS supervisor provides each task with a common access method to the VM/370 spool file system and an Execute Channel Program (EXCP) level interface for I/O to the teleprocessing line.

Printer or punch files that the VM/370 virtual machine user wants to have transmitted to a supported remote device need only be spooled to the RSCS virtual machine with the destination designated via the CP TAG command. The proper task for the remote device will be initiated and the files will be sent. For files being transmitted from the remote device to a virtual machine, RSCS will read data from the remote device, produce VM/370 spool files from the data and spool the files to the virtual machine designated by the user; these files will remain in the virtual machine's card reader until disposed of by the user.

RSCS supported remote stations are of two general types: 'non-programmable' and 'programmable'. Support is provided for both types of stations.

Non-Programmable Terminal Support

This task under RSCS provides support for the 2770, 2780, 3770 (except 3773-2 and 3773P Models) as a 2770; (3776/3777-1 also as a 3780), and 3780 terminals via the 3704/3705 Communications Controller in emulation mode only, via the 2701 Transmission Control Units, via the Integrated Communications Adapter available on the 135, 135-3, 138, or, for the 2770, 2780 and 3780 terminals, via the 2703 Transmission Control unit.

Programmable Terminal Support

Any processor now supported as a HASP workstation when programmed to run as a HASP workstation is supported as a workstation by the Spool MULTI-LEAVING (SML) support under RSCS. The DOS/VS Remote Job Entry Workstation Program (PRPQ WF0358) is also supported. Any processor running HASP, ASP, RES, JES2, and JES3 is supported as a main processor by RSCS when it itself assumes the role of a HASP programmable workstation. For specific configurations supported, refer to the HASP pages.

RSCS offers these advantages:

  • A multitasking supervisor designed to facilitate transmission of data to and from VM/370 systems.

  • Common support for the 2770, 2780, 3770 (except 3777-2) as a 2770; 3776/3777-1 also as a 3780 and 3780

  • Access to main processors running HASP, ASP, RES, JES2 and JES3.

  • Access to HASP Programmable Workstations.

  • Access to System/34 with SSP (MRJE).

  • Access to System/36 with SSP (MSRJE) or 'and MSRJE'.

  • Access to 8100/DPPX with DPPX/RJE (BSC) or 8100/DPPX/SP with DPPX/SP/RJE (BSC).

  • Multiple telecommunications workstation lines supported by one RSCS virtual machine for remote data transmission.

  • Common command language for all data control functions.

  • Command language compatible with the VM/370 system operator's spool file control commands.

  • Entry of a subset of the control commands from the remote station.

  • RSCS access security provided by password validation by the tasks of remote stations before data transmission begins.

Interactive Problem Control System - IPCS

VM/370 IPCS support is intended for use by systems programmers and IBM Program Support Representatives (PSRs).

IPCS is intended to reduce the time expended in managing and resolving programming problems and to reduce the necessity of doing problem management, problem determination and problem isolation using hardcopy documentation.

The problem management facilities provide individual disk resident problem reports and includes commands that allow viewing and updating of a disk resident problem status file. These facilities allow both the system programmer and the PSR to manage problems from their occurrence through their resolution.

Problem determination facilities standardize the problem reporting process, identify previous occurrences of the same problem on that system and allow faster and more specific identification with similar problems previously experienced by the entire VM/370 customer base. Duplicate problem recognition: 1) reduces the amount of unnecessary hardcopy documentation and 2) allows faster identification of available fixes that can be applied to the system.

Online problem isolation facilities provide the capability to view and diagnose disk resident problem related data; e.g., CP abend dumps without the use of hardcopy documentation. This allows the system programmer or PSR to interactively diagnose a CP abend dump from a VM/370 supported terminal to determine the need to output the dump in hardcopy.

VM/370 teleprocessing support allows the use of IPCS by support personnel located remotely from the customer's location. There is the dependency upon the availability of the necessary teleprocessing facilities on the customer's system and at the remote location.

VM/370 architecture provides the facilities necessary to restrict data access to any given user of the system including a PSR using IPCS facilities. It is the customer's responsibility to determine what data the system needs for protection. In allowing the PSR to work in an online environment, the system programmer using standard VM/370 facilities can control the PSR's access to only the necessary and pertinent data files associated with the problem being diagnosed.


VM/370 HIGHLIGHTS

  • Provides virtual machine and virtual storage capabilities for S/370.

  • Offers a general-purpose, conversational time sharing system suitable for problem solving, program development and end-user applications.

  • Allows many types of batch problem-solving applications to be run from a remote terminal with no change to the batch program.

  • Allows DOS/VS, OS/VS1 and OS/VS2 virtual machines, as well as those running DOS or OS, to run concurrently on the same S/370. Where your customer has specific throughput or terminal response requirements, you should plan to benchmark VM/370 to ensure that any proposed configuration will meet the customer's performance needs.

  • Allows multiple copies of the same operating system to run concurrently in different virtual machines, eliminating the need for DOS customers for example, to multitask unrelated jobs together in the same partition and permitting the use of specialized virtual machine systems.

  • Allows system generation, system update and system testing, as well as operating system conversion and testing activities concurrent with other work.

  • Provides a high degree of security, isolation and integrity for each user's operating system, programs and data. Restricts a user's capability to access or alter any portion(s) of other users' virtual machines.

  • Provides disk password protection to limit authorized access to users' disks; and read only disk protection to minimize the possibility of destruction of information or to allow shared reading of disk files.

  • Provides device address independence for all operating systems that run under the control of VM/370.

  • Provides facilities which supplement the reliability, availability and serviceability (RAS) characteristics of the S/370 architecture.

  • Allows operating systems which do not themselves support the Dynamic Address Translation facility to use virtual storage as though it were real storage.

  • Provides the ability to subdivide physical disk packs into virtual disks, each with its own virtual I/O device address, disk label, Volume Table of Contents (VTOC) and a user-specified number of contiguous cylinders starting with virtual cylinder zero.

  • Allows one or more users to test privileged code in their own virtual machines.

  • Allows new computer operators to get 'hands on' experience using a remote terminal and their own virtual machines.

  • Permits shared use by all virtual machines of the 2770, 2780, 3770 (except 3777-2) (as a 2770; 3776/3777 also as a 3780), and 3780 terminals for remote printing, punching and card reading.

  • Supports communication with other Processors running HASP, ASP, JES2, JES3, RES, the DOS/VS RJE PRPQ, DPPX/RJE, DPPX/SP/RJE and VM/370.

  • Provides the full capabilities of the 3270 to users of VS APL through support of the 3270 Data analysis APL Feature. VS APL support of the Feature aids in the interchange of APL terminal procedures and applications among APL and 3270 users by providing a consistent terminal protocol across these applications.

  • Provides options to improve the performance of selected virtual machines.

  • Provides support for a virtual and/or real channel-to-channel adapter. VM/370 can run on either or both of two processors coupled by a real channel-to-channel adapter. Support of the virtual channel-to-channel adapter allows the user to run control programs designed to operate on directly coupled systems under VM/370.

  • Allows the use of virtual machines for backup of programs currently being run on other S/360 or S/370 computers having equivalent devices but differing I/O addresses and storage size.

  • Provides the potential for programmers to increase productivity through use of the Conversational Monitor System.

  • Eliminates the need for JCL (Job Control Language) preparation in most cases when compiling, assembling and/or testing in CMS.

  • Simplifies the creation and manipulation of source programs on disk, and allows the user to examine selected portions of program listings and storage dumps at his remote terminal.

  • Allows any user to set up frequently used sequences of commands into special procedures to eliminate the repetitious re-keying of those command sequences.

  • Allows the spooling of virtual machine console input and output, including CP commands and responses.

  • Allows the use of one or more dedicated channels by any number of virtual machines depending on the total number of real channels available on the system. VM/370 must have at least one selector or block multiplexer channel for use by paging, spooling and VM/370 system residence devices. I/O devices attached to a dedicated channel can be accessed only by the virtual machine to which the channel is dedicated.

RELEASE 6 HIGHLIGHTS

  • VM/370 Support for the 3033 Attached Processor: Support for the 3033 attached processor and channel-set switching is supported.

  • VM/370 Support for the 4321, 4331, 4341 and 4361 Processors: Support for the 4321, 4331, 4341 and 4361 Processors is provided in S/370 compatibility mode.

    ECPS:VM/370 Assist is a performance option available in S/370 compatibility mode. The ECPS:VM/370 Assist and ECPS:VS1 Assist are mutually exclusive on the 4341 processor.

    Support is also provided for the new 20 line Operator Display Console (3278 mdl 2A) in both display mode and printer/keyboard mode. In printer/keyboard mode, support for 3268 Printer mdl 2 (4341 only) or 3287 Printer mdls 1 and 2 is provided.

    The Communications Adapter feature of the 4321 Processor and 4331 processor will be supported by Release 6. The SDLC line protocol of the Communications Adapter requires new programming support that is now available. This support allows a DOS/VSE guest virtual machine with ACF/VTAME active to operate in a VM/370 environment. The Start/Stop and BSC line protocols do not require additional programming support.

  • Support of the 3800 Printing Subsystem: VM/370 supports the 3800 printing subsystem as follows:

    • Use as a dedicated device: This support will allow a 3800 to be attached to a virtual machine for its exclusive use.

    • Use as a VM/370 real spooling device: VM/370 real spooling device support is extended to include support of the 3800 printing subsystem. This support allows spool files normally directed for printing on a 1403, 3211 or 3203 printer to be printed on the 3800 printing subsystem.

      VM/370 3800 printing subsystem support provides an installation with the capability to specify the following options for each spool file:

      • Selection of one character arrangement table
      • Graphic character modifications
      • One forms control buffer
      • Forms overlay (flashing)
      • Copy modifications

      Additionally, through delayed purging, VM/370 recovery procedures for spool files have been extended to be cognizant of the characteristics of the 3800 printing subsystem. Thus loss of spool files due to hardware malfunction is minimized.

  • VM/370 Support for the 3850 Mass Storage System is Extended: Virtual machines, including CMS, can access Mass Storage volumes containing VM/370 minidisks or entire Mass Storage Volumes dedicated to the virtual machine. These volumes appear to the virtual machine as 3330 volumes and are accessed using 3330 device support. Unit allocation, volume mounting and volume demounting are controlled by CP. Staging, initiated by access to a Mass Storage Volume, is normally in cylinder fault mode. Virtual Machines running OS/VS1 or MVS containing MSS support can also access Mass Storage Volumes using existing dedicated device support.

    Communication with the Mass Storage Control component of MSS is achieve by installation of either OS/VS1 or MVS in a virtual machine. The VM/370 control program (CP) will initiate volume mounts and demounts via intersystem communication with an application program running under either OS/VS1 or MVS.

  • Support for the 3203 Printer Model 5: Support is provided for the channel attached 3203 printer mdl 5 as a dedicated device to a virtual machine and as a real spooling device to CP.

  • Additional Data Collection by VM/370 Measurement Facility: The VM/370 Measurement Facility (Monitor) has been enhanced to collect the following additional data:
    • AP/UP utilization
    • Channel and device utilization
    • Storage utilization
    • Selective seeks
    • Alternate path statistics

    VM/370 Measurement Facility enhancements also include Monitor to Disk support for real time. This support will enable the system analyst to specify periodic closing of the active Monitor spool file with high enough frequency to support real time data reduction and display.

  • Journaling and Security Enhancements: Through the generation of unique accounting records, an installation may optionally track unsuccessful logon attempts as well as successful and unsuccessful link attempts.

    VM/370 security facilities have been enhanced by Release 6 with the support of forced password masking available for Link and Logon commands as an installation option.

  • Unprotected Shared Segments: With Release 6, an installation will have the option to run with shared segments unprotected. This support eliminates the overhead involved in scanning for changed shared pages in both AP and UP systems in switching page table pointers, and in maintaining duplicate copies of shared systems in an AP environment.

  • Elimination of Automatic UNSHARE Processing: VM/370 shared segment processing will be changed to eliminate the automatic UNSHARE process. With previous releases of VM/370 a shared page, once changed, was made private and given to the user. When an installation runs with protected shared segments, the user that modifies a page within a shared segment is sent a message informing him of the violation and the terminal is placed in console function mode. The changed page is returned to storage. The next reference to that page will cause a fresh copy to be brought into storage. When an installation runs with unprotected shared segments, any changes to those shared segments will not be detected by VM/370.

  • Trace Table Size as a System Generation Option: As of Release 6, an installation will have the option to override the default setting governing the size of the trace table by specifying the Trace Table size at system generation time. The size of the trace table can only be enlarged, not diminished beyond the default value.

  • Multiple Alternate Console System Generation Support: Support has been added to allow the specification of multiple alternate system consoles at system generation time. Only one alternate console specified can be active at any one point in time.

  • New CP Commands: A new CP command 'SMSG', will be available with Release 6 that provides the general user with the ability to send a message to another virtual machine's storage. That virtual machine must be prepared to receive the message. This command may be issued by either a terminal user or a program running in a virtual machine.

  • A new CP command 'VMDUMP', will be available with Release 6 that allows a virtual machine to initiate its own dumps. The output of this command is a reader spool file that can be sent from one virtual machine to another. This command may be issued by either a terminal user or a program running in a virtual machine.

RELEASE 5 HIGHLIGHTS

  • Support of the 3033 Processors: VM/370 now supports the 3033 Processor. This support includes the following:

    • Use of the channel attached consoles as primary system console and alternate console.

    • Use of the new processor numbers to determine the duration of the time slice.

    • Integrated channels.

    • CPEREP changes to recognize and process logout formats of the new processor. EREP processing has been enhanced to allow EREP processing to be independent of the content and EC level of the extended logout areas of the 3033 Processor. This is accomplished by reading frames stored on the 7443 Service Recording File and using them to format and interpret error records.

    • The CP error recording logic has been changed to allow recording on from two to nine cylinders, as specified by the user during system generation. Error record types are intermixed in the error recording area.

    Release 5 does not contain virtual support for the S/370 Extended Facility on the 303X Processors or the S/370 Extended Feature on the 158/168 Processors.

  • Support of Channel Check Reflection: Support for the reflection of channel checks has been added in Release 5. This support includes reflection of channel control checks, interface control checks and channel data checks to virtual machines.

    The support includes integrated channels on the 135, 135-3, 138, 145, 145-3, 148, 155-II, 158, 158-3, 3031, 3032 and 3033. It also includes support for the stand-alone 2860, 2870 and 2880 channels on the 165-II, 168 and 168-3 processors.

  • CMS Support of DOS/34: Release 5 contains support in CMS/DOS and CMS VSAM for new devices and new function introduced in DOS/VS Release 34.

    • Support of 3330-11 native.

    • Support of 3350 native.

    • Increase page length flexibility when producing printed output from Access Method Services.

    • Support of the 3203 Printer mdl 4 as a 3211 compatible printer.

      This support removes the restriction on use of the 3330-11 and 3350 with VSAM under CMS.

  • IPCS as a Basic Component: IPCS has been made a basic component of VM/370.

    • Separate installation of IPCS is no longer required.

    • As of Release 5, VM/370 will no longer include the VMFDUMP module DMKEDM. IPCS VMFDUMP is the improved functional replacement.

    IPCS was announced for VM/370 on January 12, 1976 in P76-2.

  • Monitor to Disk: This support provides the user with the option of recording output from the VM/370 Measurement Facility on disk. The previous support required the user to dedicate a tape drive to the Measurement Facility for those periods of time that the user wished to record performance data. The new support makes it more practical for the user to make frequent measurements. By doing so and by using the VM/370 Performance/Monitor Analysis Program FDP, the user can gain a better understanding of the operation of the system and its performance.

AP HIGHLIGHTS

The VM/370 AP support provides for concurrent execution of work on the two processors of an Attached Processor System in the following states:

  • Both processors can execute in the problem state concurrently.

  • Either processor can execute in the supervisor state while the other processor executes in the problem state.

  • In some instances both processors can execute in the supervisor state concurrently.

  • Because of the system design, all I/O requests must be issued by the host processor and all I/O interrupts will be received on the host processor.

  • The VM/370 AP support makes use of the Virtual Machine Assist feature (if present) on either or both instruction processors in an AP system.

  • The VM/370 AP support will include automatic processor recovery. If the Attached Processor is unable to function because of hardware malfunctions, VM/370 will attempt to execute in uniprocessor mode on the host processor. Should the host processor experience hardware malfunction, VM/370 will terminate operation since no I/O capabilities exist on the Attached Processor.

  • The VM/370 AP support makes use of AP hardware features including:
    • Shared Main Storage
    • Prefixing
    • Processor Signaling
    • Processor Address

HIGHLIGHTS OF RELEASE 4

  • VM/370 Support for the 3850 Mass Storage System (MSS): The Mass Storage System (MSS) is a hierarchical storage system that makes up to 472 billion bytes available online via 3330 devices. Access and storage are controlled by the 3850 Mass Storage System. The Mass Storage Control (MSC) accepts requests for Data from up to four S/370 processors. When data is no longer needed, it is moved to slower, less expensive storage medium, freeing the fast-access DASD space for current use.

    VM/370 supports up to four dedicated paths for each 3850 MSS. VM/370 dedicated MSS support allows up to four virtual machines concurrently running VS1, SVS or MVS operating systems generated with 3850 MSS support to each control an interface to a common 3850 MSS. Each of the Mass Storage Control (MSC) connections can be attached to a different VM/370 virtual machine or a different processor. Each virtual machine using an MSC port reduces by one the number of other real processors that may be connected to the 3850 Mass Storage System. Other virtual machines not using the MSS can be run concurrently.

  • Alternate Path Support: VM/370 Alternate Path Support will provide for up to four channels on one control unit to be attached to VM/370 through the use of the Two-Channel Switch and Two-Channel Switch, Additional Features. Since one device may be attached to two real control units by use of the String Switch feature, eight paths to a given device are available to the control program when the maximum number of alternate channels and alternate control units are specified.

    If the primary path to a device is busy when a I/O request is received for that device, VM/370 can select a free path, allowing for immediate I/O initiation on the available alternate path. When no available path exists for a device, the I/O request is queued off multiple busy/scheduled paths. When a path becomes available, the waiting I/O request is initiated on that path.

  • Virtual Reserve/Release Support: VM/370 will support Reserve/Release operation codes for shared DASD as though each virtual machine has a separate channel path to a shared device. The Reserve/Release operation codes will be simulated on a virtual basis for minidisks, including full extent minidisks.

  • Removal of Free Storage Abend when Adding Virtual Devices: VM/370 will no longer abend if a request for free storage cannot be obtained when virtual devices are being added to a user's configuration. Instead, an appropriate message will be issued.

  • Interactive Problem Control System (IPCS) Enhancements: Contained in Release 4 are enhancements to the IPCS VMFDUMP command and DUMPSCAN command.

  • Support of S/370 Models 158 and 168 Attached Processors: The VM/370 AP support will provide for concurrent execution of work on the two processors of an Attached Processor System in the following states:

    • Both processors can execute in the problem state concurrently.

    • Either processor can execute in the supervisor state while the other processor executes in the problem state.

    • In some instances both processors can execute in the supervisor state concurrently.

    Because of the system design, all I/O requests must be issued by the host processor and all I/O interrupts will be received on the host processor.

    The VM/370 AP support makes use of the Virtual Machine Assist feature (if present) on either or both instruction processors in an AP system.

    The VM/370 AP support will include automatic processor recovery. If the Attached Processor is unable to function because of hardware malfunctions, VM/370 will attempt to execute in uniprocessor mode on the host processor. Should the host processor experience hardware malfunction, VM/370 will terminate operation since no I/O capabilities exist on the Attached Processor.

    The VM/370 AP support makes use of AP hardware features including:

    • Shared Main Storage
    • Prefixing
    • Processor Signaling
    • Processor Address

RELEASE 3 PLC 8 HIGHLIGHTS

  • VM/370 support for the S/370 mdls 135-3, 138, 145-3 and 148 includes the standard feature of Extended Control Program Support (ECPS) which is available only on these models. This feature is an expansion of the current virtual machine assist. Extended Control Program Support is a hardware assist that reduces Processor time needed to execute certain frequently used VM/370 supervisor functions by as much as 55 percent. The performance improvement is in addition to that resulting from the improved internal instruction rate of the hardware and the current virtual machine assist. Extended Control Program Support will be used if a test performed during IPL shows it to be present and compatible, thus allowing a particular VM/370 system to be run on the newly supported models as well as on other models. Console support for the mdls 138 and 148 is provided in both display and printer/keyboard modes. The 3286 Printer mdl 2 support is provided in the printer/keyboard mode. The 3203 printer mdl 4, which is natively attached for the S/370 mdls 138 and 148, is also supported as a real or virtual device.

  • 'SET AUTOPOLL ON' substantially reduces the overhead required by CP to service BTAM auto-poll channel programs by bypassing the testing of the channel program and allowing notification to CP via a DIAGNOSE interface whenever an auto-poll CCW has been modified. (Supported by OS/VS1 Release 6 only.)

  • VM/370 support of the 3270 Data Analysis/Text Keyboard includes:

    • Extensions to the CP commands 'TERMINAL' and 'QUERY'.

    • Access to 151 characters. Included is the 120-character TN, T11 character set plus 32 graphics, code and control characters, allowing new approaches to text applications.

    • The COPY function to copy text characters from a screen to a 3284-2 or 3286-2 matrix printer (equipped with feature #1066 for hard copy printouts).

  • Support of many of the OS/VS2 EREP parameters allows the installation more flexible definition of the contents of the EREP output. Data from the error recording area can now be concatenated to data previously recorded on an output tape. Most of the original VM/370 operands have been replaced with their OS/VS2 equivalents due to conflict in meaning and usage between the original VM/370 operands and the OS/VS2 parameters. The HELP operand has been deleted.

  • The Virtual Machine Communication Facility allows virtual machines to communicate via a CP DIAGNOSE protocol. The support provides a number of functions that can be invoked by DIAGNOSE instructions to establish and control communications. These include authorization to establish communications, data transfer and signaling, and control functions. The interface is provided for use by user-written programs executing in virtual machines.

HIGHLIGHTS OF RELEASE 3

  • CMS support of VSAM provides indexed file capability to high level language programs executing under CMS, data compatibility with OS and DOS, enlarged file capacity for CMS end user applications, and record I/O for users of VS BASIC. CMS will support VSAM via integration of the DOS/VS VSAM component and simulation of DOS/VS supervisor and I/O functions. CMS support of VSAM will permit user programs written in COBOL, PL/I or VS BASIC to utilize VSAM function under CMS and will include a new command to invoke VSAM Access Method Services. Assembler program usage of VSAM function and the ISAM Interface Program (IIP) are not supported.

  • CMS support of DOS/VS program execution adds a new option to the SET command of CMS to enable the terminal user to specify the DOS environment in CMS and invoke a new set of CMS commands. In the DOS environment CMS simulates DOS/VS supervisor and I/O functions thereby allowing execution of many DOS programs. Execution of DOS programs is initiated via commands entered at the CMS terminal or via entry to the CMS Batch Facility. Assembler program execution is supported only insofar as the program utilizes DOS/VS services required in CMS for COBOL and PL/I compiler and execution library support.

  • Support of the 3270 Data Analysis-APL Feature brings increased productivity to the CMS user of VS APL through improved interactive data processing. The new Feature added to the efficiencies of the 3270 Information Display is designed to increase S/370 use by data processing professionals and to attract new applications of new users. The Feature:

    • Provides a US EBCDIC extension set for APL characters, as well as dual case, and characters of the 'TN' print train (which are displayable and printable only).

    • Retains full editing (substitute, delete, insert) and formatting capabilities of the 3270, on current and planned applications.

    • Requires minimal retraining either for keyboard/printer users of APL or for 3270 users.

    • Operates with Featured and non-Featured devices on the same Featured control unit.

    • Is orderable from the factory or installable in the field.

  • Support of the new program product VS APL provides a shared variable facility that allows APL users to communicate with non-APL programs called 'auxiliary processors' operating outside the APL environment. This provides the APL user selected data management services and selected CP and CMS command service, offering enhanced facilities for problem solving and end-user applications in CMS.

  • Support of the DOS/VS COBOL and DOS PL/I Optimizing Compiler and library program products provides additional program development and end-user application facilities in CMS to DOS-based installations.

  • Support of the new 3350 and 3344 Direct Access Storage provides VM/370 support as well as support in DOS/VS, OS/VS1, and OS/VS2 running in a VM/370 virtual machine.

  • Extended shared segment usage by CMS provides sharing of VSAM and DOS/VS supervisor and I/O functions among CMS users. In addition, the CMS editor, the EXEC command processor, and the OS simulation routines are now reentrant and can be placed in a discontiguous shared segment by the installation. CMS is utilizing CP extensions to the current support of named and saved systems to share segments which are outside the address space of a virtual machine.

  • Extended CP protection of shared segments allows the Virtual Machine Assist feature to be activated for shared, named systems, thus allowing shared CMS systems to take advantage of the performance improvements of this feature.

  • Improved spool file recovery adds a new checkpoint start procedure to the recovery options available to the VM/370 operator at IPL. Another RAS improvement includes enhancements to the procedure for generating the CPEREP program. Extended local 3270 support provides a COPY function for the 3284, 3286, 3287 (as a 3284/3286) and 3288 printers.

  • Support of the dial feature (#3440) for the 3275 Display Station mdl 2 allows the 3275 to be used over switched lines as a virtual machine operator's console.

  • The VM/370 publications library now includes: "VM/370: CMS User's Guide", "VM/370: System Logic and Problem Determination Guide", "VM/370: Operating Systems in a Virtual Machine" and "VM/370: Data Areas and Control Blocks Logic". Additional information on the 3270 Data Analysis-APL Feature is in the publication "An Introduction to the IBM 3270 Data Analysis-APL Feature" (GA27-2788).

OPTIMIZING VIRTUAL MACHINE PERFORMANCE

An operating system executing in a VM/370 virtual machine is normally slower compared to stand-alone execution on the same S/370. The operating system executes concurrently with other virtual machines and executes in problem state to allow the CP component to control the resources of the real machine. VM/370 allows an installation to improve the performance of selected virtual machines by specifying one or more of the following options:

  • Virtual Machine Assist, a hardware assist available on S/370 mdls 135, 135-3, 138, 145, 145-3, 148, 158, 158AP, 168, 168AP, the 3031, 3031AP, 3032 and 3033 Processors and the 4331, 4341 and 4361 Processors makes possible throughput improvements for virtual machine users. See "Desirable Features" under "System Configuration" for a description of the Virtual Machine Assist. Virtual Machine Assist on the 168, 168AP, 3032 and 3033 is an RPQ.

  • The S/370 135-3, 138, 145-3, 148 and the 4341 Processor include Extended Control Program Support. The Extended Control Program Support on the 4321 and 4331 is a subset of that provided on the 4341. Extended Control Program Support for VM/370 is a hardware assist that is an expansion to the current Virtual Machine Assist. This support includes an operator command to disable the new assist, allowing the user to run with the previous support, if he desires.

  • APL Assist feature, (#1005) on the S/370 mdl 135 and on the S/370 mdl 145, which may be used with the VS APL Program Product (5748-AP1) to enhance performance of VS APL under CMS on the mdls 135 and 145. APL Assist is standard on S/370 135-3, 138, 145-3, and 148. The APL Assist feature (1005) is mutually exclusive with the APL Assist RPQ (S00256) on the S/370 mdl 145.

  • APL Assist, an RPQ (S00256) on the S/370 mdl 145 which may be used with VS APL (5748-AP1) to enhance performance of APL under CMS on the mdl 145.

  • Favored Execution, an option which attempts to provide a specified percentage of real processor time to a particular virtual machine.

  • Reserving 'n' number of page 'frames' (i.e., 4,096 byte blocks) of real main storage for the exclusive use of one virtual machine to minimize paging in that virtual machine.

  • Designating the virtual machine as 'Virtual = Real', to eliminate paging in that virtual machine and to reduce the normal control program overhead. This is accomplished by giving that virtual machine a contiguous block of real main storage equal in size to its virtual storage and at real storage addresses which correspond to its virtual addresses, with the exception of page zero (i.e., the first 4,096 bytes of storage). Page zero is relocated, but locked into real storage.

  • Locked page frames.

  • Assigning higher priorities to one or more virtual machines.

The options of favored execution, with a percentage specified, reserved page frames and V=R, listed above, can be specified for only one virtual machine at a time. Three different virtual machines may each have one of these three options, or several options may be specified for the same virtual machine.

There is no VM/370 restriction on the number of virtual machines that may simultaneously use the Extended Control-Program Support for VM/370, Virtual Machine Assist, the APL Assist, and the locked page frame or priority options. Locked page frames are restricted by the amount of real storage available. Use of any or all of these options, except for the Extended Control-Program Support for VM/370, Virtual Machine Assist and the APL Assist, will reduce the performance of other virtual machines.

For a more detailed description of these performance options, see the "IBM Virtual Machine Facility/370: Introduction" (GC20-1800), or the "IBM Virtual Machine Facility/370: System Programmer's Guide" (GC20-1807).

OS/VS1 improvements under VM/370, VM/VS Handshaking, will enable VS1 when running under VM/370 to enhance its operational characteristics and to avoid many instructions and procedures which are redundant in a virtual machine environment. With this support, handshaking will be initiated automatically during nucleus initialization of VS1 when running under VM/370 if the VS1 system has been generated with a new VS1 option call 'VM'. In handshaking mode, VS1 will:

  • Close CP spool files at job end to permit VM/370 to begin final output processing earlier.

  • Provide a unique mode of execution which will eliminate paging by VS1 and reduce the number of privileged instructions executed whenever the virtual machine size is equal to the VS1 virtual address space. This mode makes possible performance improvements for VS1 where address space is less than or equal to 16Mb under VM/370 by reducing the real supervisor state time necessary to control the operation of the VS1 virtual machine.

  • Optionally process a new virtual interrupt that allows VM/370 to return control to the VS1 virtual machine prior to resolution of a real page fault. The VS1 supervisor may then perform a task switch to allow other tasks access to the system.

Final evaluation of the performance of each operating system under VM/370 must be made in terms of each installation's throughput requirements and of the function provided by concurrently executing virtual machines.


INTEGRATED EMULATORS UNDER VM/370

Emulator-dependent programs which run on a particular S/370 equipped with the appropriate compatibility feature(s) listed below can be run on that S/370 in DOS or OS virtual machines under VM/370.

The following chart shows by S/370 Model number which integrated emulators can run under VM/370 and the compatibility feature numbers that are required:

1401 1440 1401 1460 1440 1410 7070 System 1460 7010 7074

135,135-3,138 #4457 145,145-3,148 #4457 #4458 155II,158,158AP #3950(2) #7117 (1,2) 165II #7117 168,168AP #7127 4331 #3950

709 7090 S/360 7094 Mdl System 7080 7094II 20

135,135-3,138 #7520 165II #7118 #7119 168,168AP #7128 #7129

No changes are required to these emulators, DOS, OS, or to VM/370 itself to allow emulator-dependent programs to run in virtual machines.

  1. For the mdl 158 only, this feature is not available if the Virtual Machine Assist feature (#8740) is loaded. See "System Configuration" section.

  2. For the mdl 158 only, this feature is not available if the OS/VS1 ECPS (Extended Control Program Support) Feature (#8750) is loaded.

Integrated emulators will not be supported on the 3033 processor.

Simulated Hands-On Processor Console Debugging

To aid programmers in solving obscure or complex problems that are difficult to isolate in any other way except by hands-on debugging at the processor console, VM/370 offers the following console debugging facilities from the user's remote terminal:

  • Examining or altering the contents of the following: Real or virtual storage, general registers, floating-point registers, the instruction counter and other fixed-location fields such as Program Status Words (PSWs) and the Channel Status Word (CSW).

  • Dumping on the high-speed printer the contents of all registers plus any part of storage, and selected blocks of disk records.

  • Setting an Instruction Address Stop to stop execution of the user's program at a predetermined point in the program.

  • Simulating external or I/O interrupts to the user's virtual machine (e.g., pressing the external interrupt key or readying the card reader).

  • Dynamically tracing any or all of the following:
    • I/O events
    • Successful branches
    • Supervisor Call Interrupts (SVCs)
    • User program check interrupts
    • Channel command sequences
    • Total instruction trace

Service Classification

VM/370 is System Control Programming (SCP). Refer to sales manual GI section for a detailed description of SCP support. VM/370 does not alter or affect in any way the current service classification of any IBM operating system, language, program product or any other type of IBM program supported by VM/370 while under the control of VM/370.


PROGRAMS SUPPORTED IN VM/370 VIRTUAL MACHINES

For information on those programs and program products supported to run under an operating system such as OS or DOS in a virtual machine environment under VM/370, see the appropriate pages. In addition, the RSCS Networking program product (5748-XP1) executes in a VM/370 virtual machine. See the appropriate sales manual pages for details.

System Extensions Program Products Supported by VM/370 SCP

The VM/Basic System Extensions program product (5748-XX8) and the VM/System Extensions program product (5748-XE1) extend the services and facilities of the VM/370 System Control Program. For information on these program products see the appropriate pages.

IBM Program Product Support For VM/370-CMS

The IBM program products supported under CMS are as follows:

  • OS Full American National Standard COBOL Version 4 Compiler and Library 5734-CB2
  • OS Full American National Standard COBOL Version 4 Library 5734-LM2
  • OS/VS COBOL Compiler and Library 5746-CB1(1)
  • OS/VS COBOL Library Only 5746-LM1(1)
  • COBOL Interactive Debug 5734-CB4(1)
  • DOS/VS COBOL Compiler and Library 5746-CB1(5)
  • OS FORTRAN IV (G1) 5734-FO2
  • OS FORTRAN IV Library (Mod I) 5734-LM1
  • OS Code and Go FORTRAN 5734-FO1
  • OS FORTRAN IV (H Extended) 5734-FO3
  • OS FORTRAN IV Library (Mod II) 5734-LM3
  • FORTRAN Interactive Debug 5734-FO5
  • OS PL/I Optimizing Compiler 5734-PL1
  • OS PL/I Resident Library 5734-LM4
  • OS PL/I Transient Library 5734-LM5
  • OS PL/I Optimizing Compiler and Libraries 5734-PL3
  • OS PL/I Checkout Compiler 5734-PL2(2)
  • DOS PL/I Optimizing Compiler 5736-PL1(5)
  • DOS PL/I Resident Library 5736-LM4(5)
  • DOS PL/I Transient Library 5736-LM5(5)
  • DOS PL/I Optimizing Compiler and Libraries 5736-PL3(5)
  • VS BASIC 5748-XX1(3)
  • MATH/BASIC 5734-XM8
  • STAT/BASIC 5734-XA3
  • Business Analysis/BASIC 5734-XMB
  • Planning System Generator/CMS (PSG/CMS) 5748-XT1
  • APL/CMS 5799-ALK(4)
  • VS APL 5748-AP1
  • Document Composition Facility 5748-XX9(6)
  • Data Language/1 DOS/VS Version 1 Release 4 5746-XX1
  • DOS/VS RPG Release 3 5746-RG1
  • VM/370 Directory Maintenance Program Product 5748-XE4
  • Display Management System for CMS 5748-XXB
  • Interactive File System 5748-XXC

Notes:

  1. COBOL Interactive Debug operates as a command processor under CMS on programs produced by the following compilers using the TEST option:
    • OS Full American National Standard COBOL Compiler Version 4 Release 1 Modification Level 2 (5734-CB2)
    • OS/VS COBOL (5740-CB1)
  2. CMS supports the OS PL/I Checkout Compiler Release 2, Modification Level 1 and above.
  3. VS BASIC is the recommended BASIC product for use with VM/370 CMS. CALL-OS BASIC Release 1.2 under CMS is withdrawn and no longer orderable in any form. All correct BASIC programs that run under CMS with CALL-OS BASIC, 360A-CX-44X, will run under CMS with VS BASIC after adjustment of file input/output statements. CMS editing commands can be used to change these statements to conform to VS BASIC syntax. Additionally, under CALL-OS BASIC, if an OPEN statement is issued for a file already open, the file is repositioned to its beginning. Under VS BASIC, an OPEN statement for a file already open is ignored. CALL-OS BASIC programs containing such OPEN statements should be converted by adding a CLOSE statement before the OPEN statement. Files created under CALL-OS BASIC which run under CMS can be read by VS BASIC after being converted to VS BASIC format using the VS BASIC service program VSBUTIL. A new VS BASIC release was available on 4/26/76. This new release, in conjunction with Release 3 of VM/370 CMS, removes the restriction on the use of record input/output for users of VS BASIC under CMS.
  4. VS APL Program Product (5748-AP1) makes the APL language available to CMS users under VM/370 on any virtual storage S/370 Processor and 3031, 3031AP, 3032, and 3033 Processor except 3115 and 3125. This system provides language, function and performance enhancements over the APL/360 systems. In addition, a no charge RPQ for the S/370 mdl 145 is available to enhance the performance of VS APL (5748-AP1) on the mdl 145. The APL Assist (#1005) for the mdl 145 can be ordered directly through AAS. Note: APL Assist is standard on the S/370 mdls 135-3, 138, 145-3, and 148.
  5. CMS support is as of VM/370 Release 3.
  6. The Document Composition Facility consists of a general document handling program, called SCRIPT/VS, and an optional feature called the Foreground Environment Feature. SCRIPT/VS can be run directly in the foreground of CMS with the Foreground Environment Feature installed.

For program product ordering information, see the respective program product pages. Further details on the languages supported appear in the publication "IBM Virtual Machine Facility/370: Introduction" (GC20-1800), and in the Program Product section.

Installed User Programs

SCRIPT/370 Version 3 (5796-PHL), an Installed User Program (IUP), is available to provide text-processing capabilities directly under CMS. See Availability Notice G320-1520.

The Statistics Generating Package for VM/370, or VM/SGP (5796-PDD), an IUP, is available and consists of a data selection and reporting language, a translator, and a library of reduction programs to handle most classes of VM Monitor output from the VM/370 Measurement Facility.

VM/370 Performance Monitor Analysis FDP (5798-CPX) is available for reduction of VM Monitor output from the VM/370 Measurement Facility.

MUSIC III, the McGill University System for Interactive Computing (5796-AJC), an IUP, is available and can complement CMS when run under VM/370 by providing a high-performance limited-function time sharing subsystem. See Availability Notice G320-1408-3.

VS/REPACK (5796-PDZ), an IUP, allows the user to collect and graphically display the pattern of activity of the program or system, analyze this data to predict how rearranging will increase efficiency and verify that the program is operating correctly.

Field Developed Programs

The VM/370 Control and Accounting System (5798-AYP), a Field Developed Program (FDP), is available for use under CMS. (See Announcement GB21-1110 for details.)

The CMS Sort for VM/370, an FDP, is available for use under CMS. See Announcement GB21-1376 for details.


CUSTOMER RESPONSIBILITIES

  1. Ordering and installing all the required communications facilities.

  2. Generating the appropriate 3704/3705 Communications Controller programs.

  3. Allocating and formatting direct access storage space for the VM/370 control program, the CMS system residence area, and user work areas.

  4. Generating and updating user directory and virtual machine descriptions.

  5. Making the final evaluation as to which programs should be run under VM/370 in his environment.

  6. Training personnel to operate the VM/370 system.

  7. Teaching users VM/370 commands and how to operate the remote terminals.

  8. For existing CP-67/CMS customers, planning for the conversion from the S/360 mdl 67 to the S/370.

It is recommended that a customer system programmer become familiar with the internal operation of the VM/370 system in order to obtain maximum benefit from the virtual machine environment.


COMPATIBILITY STATEMENT FOR CP-67/CMS USERS

VM/370 is based on the CP-67/CMS system and is designed specifically for the S/370. The Dynamic Address Translation facility on the S/370 is conceptually similar to the same feature on the S/360 mdl 67, but differs in hardware implementation. Consequently, CP-67/CMS is not supported on the S/370, and, likewise, VM/370 is not supported on the S/360 mdl 67.

The internal structure of VM/370 differs from that used in CP-67/CMS. User modifications to CP-67/CMS are not compatible with VM/370.

The Conversational Monitor System of VM/370 is based on the Cambridge Monitor System of CP-67/CMS. Some commands are unchanged, but most have additional parameters or options which offer enhanced function and more precise control. Some command names have been changed or dropped with functions moved to other commands in the Conversational Monitor System.


SPECIFIED OPERATING ENVIRONMENT

Hardware Requirements

The following systems and devices are supported by VM/370 except as otherwise noted below:

Processors

  • IBM S/370 mdl 135
  • IBM S/370 mdl 135-3
  • IBM S/370 mdl 138
  • IBM S/370 mdl 145
  • IBM S/370 mdl 145-3
  • IBM S/370 mdl 148
  • IBM S/370 mdl 155II
  • IBM S/370 mdl 158
  • IBM S/370 mdl 158-3
  • IBM S/370 mdl 158 Attached Processor
  • IBM S/370 mdl 158MP (see note)
  • IBM S/370 mdl 165II
  • IBM S/370 mdl 168
  • IBM S/370 mdl 168 Attached Processor
  • IBM S/370 mdl 168MP (see note)
  • The IBM 3031 Processor
  • The IBM 3031 Attached Processor
  • The IBM 3033 Attached Processor
  • The IBM 3032 Processor
  • The IBM 3033 Processor
  • The IBM 3033 MP (see Note)
  • The IBM 4321 Processor and 4331 Processor (except devices attached via the 4331 Loop Adapter)
  • The IBM 4341 Processor

Note: IBM S/370 mdls 158MP, 168MP and 3033MP are supported when running in uniprocessor mode, or with an asymmetric I/O configuration. In an asymmetric I/O configuration, all I/O attached to the system must be attached to one processor.

As of Release 5, the 303X processors will be supported. All S/370 Processors must have at least 393,216 (384K) bytes of real main storage.

Required Processor and Channel Features and Facilities:

  • The System Timing facility (#2001) (which includes the Clock Comparator and the CPU Timer) on mdls 135 and 145. (Clock Comparator and CPU Timer are standard on S/370 mdls 135-3, 138, and 148. They are a prerequisite on the mdl 145-3.)

  • The Floating Point feature:
    • For the 135, feature (#3900) (Note)
    • For the 145, feature (#3910) (Note)

    Note: Floating-Point Arithmetic is standard on S/370 mdls 135-3, 138, 145-3, and 148. Extended Procession Floating-Point is standard on S/370 mdls 138, 145-3, and 148 and the 4321, 4331, 4341 and 4361 Processors.

  • The Channel Indirect Data Addressing features on each of the following stand-alone I/O channels on the mdls 165II, 168, and 168AP: 2860 (#1861, #1862, #1863), 2870 (#1861), 2880 (#1861, #1862).

  • The Word Buffer feature (#8810), available with the S/370 mdl 145, is required for selector channels if a 2305 mdl 2 Fixed Head Storage Device or any model of the 3340 DASF is attached.

    Note: Word Buffer is a prerequisite on S/370 mdl 145-3 and is standard on S/370 mdl 148.

Desirable Processor Features:

  • Virtual Machine Assist. Throughput improvements for VS systems running under VM/370 are possible with a hardware assist available on the S/370 processors 3135, 3135-3, 3138, 3145, 3145-3, 3148, 3158, 3158AP and 3168, the 3031, 3031AP, 3032 and 3033 processors and the 4321, 4331 and 4341 Processors. VMA on the 3168, 3032 and 3033 is an RPQ. The Virtual Machine Assist makes performance improvements possible by allowing a significant reduction in the real supervisor state time used by VM/370 to control the operation of virtual machines running under VM/370.

    This reduction in VM/370 supervisor state time is accomplished by using emulation, rather than software simulation, for certain privileged operation codes used by the VS system supervisors. Emulation is also used to update the shadow page table and to handle SVC interrupts.

    The Virtual Machine Assist is available on the S/370 mdls 135, 145 and 158 as a hardware feature (#8740), on the mdl 168 as an RPQ (S20573), on the 3032 as an RPQ (8P0723) and on the 3033 as an RPQ (EJ1156 and S20587). It is standard on the S/370 mdls 135-3, 138, 145-3, 148, the 3031 and 3031AP Processors and on the 4331 and 4341 Processors. On the S/370 mdl 158AP, Virtual Machine Assist function is also included in and enabled by OS/VS1 ECPS (Extended Control Program Support) Feature (#8750). Contact your Product Marketing Group for further information on availability of the RPQ. See the "Machines" section for details on the availability of the hardware feature. On the S/370 mdl 158 VMA Function is also included in and enabled by OS/VS1 ECPS (Extended Control-Program Support) Feature (#8750).

  • The IBM S/370 135-3, 138, 145-3, and 148 and the 4321, 4331, 4341 and 4361 Processors include Extended Control Program Support. The Extended Control Program support on the 4321/4331/4361 Processors is a subset of that provided on the 4341. A hardware assist has been added as an expansion to the current Virtual Machine Assist. This support will include an operator command to disable the new assist, if desired. Extended Control Program Support for VM/370 is an expansion of Virtual Machine Assist to further reduce the real supervisor state time used by VM/370 while performing its control functions. The reduction in VM/370 supervisor state time is accomplished in three ways:

    1. Certain privileged instructions are emulated by the hardware rather than simulated by the software.

    2. A hardware assist has been implemented for VM/370 that is designed to be executed only by VM/370.

    3. Extended Control Program Support for VM/370 also includes support of an interval timer in a virtual machine.

  • The Extended Precision Floating Point feature, although not required, will improve the execution of programs which use Extended Precision Floating Point instructions under VM/370 on mdls 135, 155II and 158.
    • For the 135, feature #3840
    • For the 155II, feature #3700
    • For the 158, feature #3700

    The Extended Floating Point Function is also included in and enabled by OS/VS1 ECPS (Extended Control Program Support) Feature (#8750).

    The OS/VS1 ECPS (Extended Control Program Support) (#8750) cannot be used when VM/370 is running in the Attached Processor mode.

    Note: Floating Point Arithmetic is standard on S/370 mdls 135-3, 138, 145-3, 148, 3031 and 3031AP. Extended Precision Floating Point is standard on S/370 mdl 138, 145-3, 148 and the 4321, 4331 and 4341 Processors.

  • The Word Buffer feature (#8810), on the S/370 mdl 145, is recommended for selector channels if 2314 Storage Units are attached and required if 3330 (with the Integrated File Adapter), 3340, 3344 or 3350 Disk Storage units are attached.

    Note: Word Buffer is a prerequisite on S/370 mdl 145-3 and is standard on S/370 mdl 148.

Software Requirements

VM/370 is written in S/370 Assembler Language and uses S/370 instructions not available on the S/360. All program releases and SCP programming support will use CMS as an installing and updating vehicle.

VM/370 I/O SUPPORT

Direct Access Storage Devices:

  • 2314 Direct Access Storage Facility
  • 2319 Disk Storage
  • 3330 Disk Storage mdls 1, 2, and 11
  • 3333 Disk Storage and Control mdls 1 and 11
  • 3340 Direct Access Storage Facility, mdls A2, B1 and B2; and the 3348 Data Module, mdls 35, 70 and 70F
  • 3344 Disk Storage mdls B2 and B2F
  • 3350 Disk Storage mdls A2, A2F, B2, B2F, C2 and C2F
  • 2305 Fixed Head Storage mdl 1 (Processors 3165II, 3168, 3168AP and 3033 only)
  • 2305 Fixed Head Storage mdl 2
  • 3850 Mass Storage System

All of the above direct access devices with the exception of the 3850 Mass Storage System are supported as VM/370 system residence, paging and spooling devices. All except the 2305 are supported by CMS and RSCS.

Direct Access Control Units:

  • 3345 Integrated Storage Control mdls 3, 4, and 5 on the mdl 145 for 3330 Disk Storage mdls 1 and 2; 3333 Disk Storage and Control mdls 1 and 11 and 3340 mdl A2
  • 2835 Storage Control mdl 1 for 2305 mdl 1 (Processors 3165II, 3168, 3168AP, 3031, 3032, 3033 only)
  • 2835 Storage Control mdl 2 for 2305 mdl 2
  • 2844 Auxiliary Storage Control for 2314 and 2319
  • 3830 Storage Control mdl 1 for 3330 mdls 1 and 2 only
  • 3830 Storage Control mdl 2 for 3333 mdls 1 and 11 and 3340 mdl A2
  • 3830 Storage Control mdl 3
  • 3851 Mass Storage Facility
  • IFA (Integrated File Adapter) (#4650) on S/370 mdls 135, 135-3, and 145 for 2319
  • IFA (Integrated File Adapter) (#4655) on the mdl 135, 135-3, 138, for 3330 mdls 1, 2 and 11, 3333 mdls 1 and 11, 3340 mdls A2, B1 and B2, and 3344 mdls B2 and B2F
  • ISC (Integrated Storage Control) (#4460) on the mdls 145, 145-3, 148, 155II and 168 for 3330 mdls 1, 2 and 11, 3333 mdls 1 and 11, 3340 mdls A2, B1 and B2, 3344 mdls B2 and B2F, and 3350 mdls A2, A2F, B2, B2F, C2 and C2F.
  • DASD Adapter (#3201) of the IBM 4321/4331/4361 with attached 3340-A2, B2, B2F, 3344-B2, B2F

Magnetic Tapes:

  • 2401, 2402, and 2403 Magnetic Tape Units
  • 2415 Magnetic Tape Unit, mdls 1, 2, 3, 4, 5 and 6
  • 2420 Magnetic Tape Unit, mdls 5 and 7
  • 3420 Magnetic Tape Unit, mdls 3, 4, 5, 6, 7 and 8
  • 3410 Magnetic Tape Unit, mdls 1, 2, and 3, 9-track only
  • 3411 Magnetic Tape Unit and Control, mdls 1, 2 and 3, 9-track only

Tape Control Units:

  • 2804 Tape Control
  • 2803 Tape Control
  • 3803 Tape Control
  • 3411 Magnetic Tape Unit and Control
  • 3088 Multisystem Channel Communication Unit, mdls 1 and 2

Printers:

  • 1403 Printers mdls 2, 3, 7 and N1 (with minimum of 132 print positions)
  • 1443 Printer mdl N1 (with 144 print positions)
  • 3203 Printer mdl 4
  • 3203 Printer mdl 5
  • 3211 Printer (Right Indexing only)
  • 3213 Printer (in 3215 Emulator Mode)
  • 3284 Printer mdls 2 and 3
  • 3286 Printer mdls 2 and 3
  • 3287 Printer mdls 1 and 2 (as a 3284/3286)
  • 3288 Printer mdl 2
  • 3800 Printer

Readers/Punches:

  • 2501 Card Reader mdls B1 and B2
  • 2540 Card Read Punch mdl 1
  • 3505 Card Reader mdls B1 and B2
  • 3525 Card Punch mdls P1, P2 and P3
  • 2520 Card Punch mdls B2 and B3

Unit Record Control Units:

  • 2821 Control Unit
  • 3811 Printer Control Unit
  • IPA (Integrated Printer Adapter) (#4670, #4672 or #4677) on the 3135 Processor
  • IPA (#4670, #4672, #4677, #8075 or #8076) on the 3138 processor
  • IPA (#8075 or #8076) on the 3148 processor

TELECOMMUNICATIONS SUPPORT SUMMARY

Terminals

The following devices are supported as virtual machine operator consoles (and consequently as CMS user terminals):

  • 2741 Communication Terminal
  • 1050 Data Communication System
  • 3101 Display Terminal (mdls 10, 12, 13, 20, 22, 23) on switched lines 100-1200 bps
  • CPT-TWX (mdl 33/35) Line Control Type Terminals
  • 3232 Keyboard Printer (mdl 51) on switched lines at 200-1200 bps
  • 3275 Display Station (mdl 2)
  • 3277 Display Station (mdl 2) via a 3271 Control Unit (mdl 2) or a 3272 Control Unit (mdl 2)
  • 3767 Communication Terminal (as a 2741)
  • 5100/5110 Computer System (as a 2741)
  • IBM S/370 mdl 138 Display Console printer-keyboard is supported in printer-keyboard mode (3286-2 required) or display mode
  • IBM S/370 mdl 148 Display Console printer-keyboard is supported in printer-keyboard mode (3286-2 required) or display mode
  • 3066 System Console mdls 1 and 2 for S/370 mdls 165II and 168
  • 3036 Console for 3031, 3032 and 3033 Processors
  • 3278 mdl 2A/3279 mdl 2C Console for the 4331, 4341 and 4361
  • 6733 Typewriter Communication Module as a CPT/TWX 33/35 on switched and nonswitched lines at 110, 150, 300 and 1200 bps

Supported by VM/370 Remote Spooling Communications Subsystem (RSCS):

  • 2770 Data Communication System
  • 2780 Data Transmission Terminal
  • 3770 Data Communication System, (except 3777-2) non-programmable models as a 2772;3776/3777-1 also as a 3780; 3777-2 as a S/360-20)
  • 3780 Data Communications Terminal
  • HASP supported programmable workstations
  • System/34 with SSP (MRJE)
  • System/36 with SSP and MSRJE
  • 8100/DPPX with DPPX/RJE (BSC)
  • 8100/DPPX/SP with DPPX/SP/RJE (BSC)

Terminal Control Units:

  • 3271 Control Unit mdl 2
  • 3272 Control Unit mdl 2
  • 8100/DPPX with DPPX/DSC (as a 3271)
  • 8100/DPPX/SP with DPPX/SP/DSC (as a 3271)
  • System/34 (as a 3271)

Transmission Control Units:

  • ICA (Integrated Communications Adapter) (#4640) available on the mdls 135, 135-3, 138
  • 2701 Data Adapter Unit
  • 2702 Transmission Control
  • 2703 Transmission Control
  • 3704 Communications Controller
  • 3705-I Communications Controller
  • 3705-II Communications Controller
  • 4321 Level 19 at shipment of processor
  • 4331/4361 Communication Adapter (#1601)

VM/370 supports the 3704 and 3705 Communications Controllers in network control mode, emulation mode, or in network control or emulation mode of the Partitioned Emulation Programming (PEP) extension of NCP/VS. CMS supports the generation of 3704/3705 programs for these modes of operation and CP provides commands to load, dump, trace and control the operation of the 3704/3705.

The 3704 or 3705 in network control mode or in the network control mode of PEP may be used by VM/370 for the control of virtual machine operator's consoles. Concurrent with the use of the network control mode of PEP by VM/370, the emulation mode of PEP may be used by multi-access virtual machine operating systems.

Use of network control mode by a virtual machine operating system requires that the 3704 or 3705 be dedicated to the virtual machine. The 3704 or 3705 may be attached to a virtual machine running DOS/VS, OS/VS1 or OS/VS2 with either VTAM or TCAM to support the network control mode of operation. In this case, communications between the 3704/3705 and the terminals attached to it are completely under the control of the virtual machine operating system, not VM/370.

Note: Customers using VM/370 support for the 3704/3705 must order one of the two OS/VS 3704/3705 Network Control Program Support Packages listed below. These are the only 3704/3705 support packages that contain the CMS files required for generating and loading 3704/3705 control programs.

  1. 5744-BA1 (supported by VM/370 in network control mode, emulation mode, or in network control or emulation mode of PEP)

  2. 5744-BA2 (Supported by VM/370 in emulation mode only)

RPQ AVAILABILITY

Prior availability of an RPQ does not guarantee or imply current or future availability. Refer to the General Information section of the sales pages for order information concerning the RPQs mentioned below.


TERMINALS SUPPORTED AS VIRTUAL MACHINE OPERATOR CONSOLES

Terminals which are equivalent to those explicitly supported may also function satisfactorily. The customer is responsible for establishing equivalency. IBM assumes no responsibility for the impact that any changes to the IBM-supplied programs or products may have on such terminals.

  1. The following system consoles and the remote terminals listed below in items 2, 3, 4, 5 (excepting those terminals attached via binary synchronous lines) and 6 are supported by VM/370 as real as well as virtual Processor operator's consoles:
    • 3210 Console Printer-Keyboard mdls 1 and 2
    • 3215 Console Printer-Keyboard mdl 1
    • 2150 Console with 1052 Printer-Keyboard mdl 7
    • IBM S/370 mdl 138, 148, and 158 Display Console printer-keyboard is supported in printer-keyboard mode (3286-2 required) or in display mode.
    • 7412 Console (via RPQ AA2846) with 3215 Console Printer-Keyboard mdl 1
    • 3066 System Console mdls 1 and 2 for S/370 mdls 165II and 168
    • 3066 System Console mdl 3 for S/370 mdl 168AP
    • 3036 Console for the 3031, 3032 and 3033 Processors
    • 3278 mdl 2A/3279 mdl 2C Console for the 4331 and 4341 Processors

  2. 2741 Communication Terminal on either switched or point-to-point nonswitched lines with these features:
    • PTTC/EBCD (#9571, P/N 1167963) or standard Correspondence #9812, P/N 1167043) print elements
    • Transmit Interrupt (#7900) or Transmit Interrupt Control RPQ (E40681)
    • Receive Interrupt (#4708)

    Required with switched lines:

    • Data Set Attachment #9114
    • Dial-Up (#3255)

    One of the following is required for point-to-point nonswitched lines:

    • Data Set Attachment (#9115 for facility D1)
    • Data Set Attachment (#9116 for facility B2)
    • Data Set Attachment (#9120 for facility B1 or D1)
    • IBM Line Adapter (#4635 for 4-wire limited distance line)
    • IBM Line Adapter (#4691-#4694 for 4-wire shared nonswitched line)
    • IBM Line Adapter (#4647 for 4-wire nonswitched line)

    The following features, although not required, will enhance the convenience and usability of the terminal:

    • Print Inhibit (#5501)
    • Red Ribbon Control RPQ (868019)
    • Typamatic Keys (#8341)
    • Pin Feed Platen (#9509)

  3. 1050 Data Communication System on either switched or point-to-point nonswitched lines with these components:

    • 1051 Control Unit (mdl 1 or 2) with these features:
      • Transmit Interrupt (#7900) or
      • Transmit Interrupt Control RPQ (E26903)
      • Receive Interrupt (#6100) or
      • Receive Interrupt Control RPQ (E27428)
      • Text Time-Out Suppression (#9698)
      • First Printer Attachment (#4408)

    Required with switched lines: Data Set Attachment #9114

    One of the following is required for point-to-point nonswitched lines:

    • Data Set Attachment #9115 for facility D1
    • Data Set Attachment #9116 for facility B2
    • Data Set Attachment (#9120 for facility B1 or D1)
    • IBM Line Adapter #4691-#4694 for 4-wire shared nonswitched line
    • IBM Line Adapter #4647 for 4-wire nonswitched line
    • 1052 Printer-Keyboard (mdl 1 or 2) with the following feature: PTTC/EBCD print element #9571, P/N 1167963

    The following features, although not required, will enhance the convenience and usability of the terminal:

    • Automatic Ribbon Shift and Line Feed Select (#1295)
    • EOB on Carrier Return RPQ (E28235)

  4. Terminals on switched lines compatible with the line control used by the IBM Telegraph Control Type II Adapter (8-level ASCII code at 110 bps).

    • The 3101 Display Terminal (mdls 10, 12, 13, 20, 22, 23) is supported on switched lines at 100-1200 bps as a virtual machine console.

    • The 6733 Typewriter Communication Module is supported as a CPT-TWX 33/35 on switched lines at 110, 150, 300 and 1200 bps.

    • 3232 Keyboard Printer (mdl 51) is supported on switched lines at 300-1200 bps.

  5. 3270 Information Display System with these components, including the Data Analysis-APL Feature (#1066) if APL or text characters are to be displayed or printed via copy.

    3271 Control Unit mdl 2 on nonswitched, point-to-point, binary synchronous transmission lines.***

    3272 Control Unit mdl 2 on a multiplexer, block multiplexer or selector channel.

    3277 Display Station mdl 2 with one of the following features required by VM/370:

    • 66-Key EBCDIC Typewriter Keyboard (#4630)**
    • 66-Key EBCDIC Data Entry Keyboard (#4631)
    • 78-Key Operator Console - Keyboard (#4632)
    • 78-Key EBCDIC Typewriter Keyboard (#4633)
    • 66-Key EBCDIC/APL Typewriter Keyboard (#4637)**
    • 78-Key EBCDIC/APL Typewriter Keyboard (#4638)
    • 78-Key Text Keyboard (#4639)

    The following features, while not required, will enhance the convenience and usability of the terminal:

    • Audible Alarm (#1090)
    • Operator Identification Card Reader (#4600)
    • Lowercase Character Display RPQ (8K0366)

    The following feature recommended for use with either Keyboard 4637 or 4638 only, provides APL, dual case US EBCDIC, and (output only) TN print train capability; used with keyboard #4639, it provides access to the 120 TN, T11 character set: Data Analysis-APL (#1066).

    3275 Display Station mdl 2 with the same features required as the 3277 mdl 2. The Data Analysis-APL Feature (#1066) and the EBCDIC/APL Typewriter Keyboards do not apply to the 3275. 3275 includes its own control unit function and is supported when attached via nonswitched, point-to-point, binary synchronous transmission lines or via switched connection if the 3275 is equipped with feature #3440.***

    3284 Printer mdls 2 and 3*

    3286 Printer mdl 2*

    3287 Printer mdls 1 and 2 (as a 3284/3286)

    3288 Printer mdl 2*

    * The 3284, 3286, 3287 (as a 3284/3286) and 3288 Printers are supported by VM/370 only to the extent of the COPY function which allows transferring display screens of data from local and remote 3270 system terminals to hard copy printers. The COPY function is invoked by depression of a program function key. The remote support is effective only when both the printers and the terminals are attached via the same 3271 Control Unit mdl 2 or 3275 Display Station mdl 2.

    ** These display terminals are not supported for use with the 3284, 3286, 3287 (as a 3284/3286) or 3288 printers.

    *** The maximum number of binary synchronous transmission lines supported by the CP component of VM/370 for its own use is 16 minus the number of 3704/3705 Communications Controllers operating in network control mode.

    **** The APL Feature is not available for the 3288 printer.

    3767 Communication Terminal (as a 2741) on switched or point-to-point nonswitched lines with these features:
    • 2741 Start/Stop (#7113)
    • Correspondence Keyboard #9381, or
    • EBCDIC Keyboard #9391
    • EIA Interface with Clock (#3719), or
    • 1200 bps Integrated Modem (#5500 or #5505)

  6. 5100 Portable Computer (as a 2741) on switched or point-to-point nonswitched lines with the Communications Adapter (#1525).

TERMINALS SUPPORTED FOR REMOTE SPOOLING

The VM/370 Remote Spooling Communications Subsystem (RSCS) supports the following terminals and workstations:

  1. 2770 Data Communication System. The 2770 Data Communication System with the 2772 Multipurpose Control Unit (hereafter called 2770) can be connected to the central S/370 via a switched or nonswitched point-to-point communication line.

    The following devices and features are required for operating a 2770 as an RSCS non-programmable terminal:

    • One 2213 Printer mdl 2 or one 2203 Printer or one 1053 Printer
    • One 2502 Card Reader, mdl A1 or A2
    • EBCDIC Transmission Code

    Other supported equipment and features are as follows:

    • One 545 Output Punch, mdl 3 or 4, with or without (#3950) attachment
    • EBCDIC Transparency (#3650)
    • Additional Buffer Expansion (#1491)
    • Space Compression/Expansion (#6555)
    • Synchronous Clock (#7705)

  2. 2780 Data Transmission Terminal. The IBM 2780 Data Transmission Terminal, mdl 1 and 2, can be connected to the central S/370 via a switched or nonswitched point-to-point line. EBCDIC Transmission Code is required.

    The following features are optional:

    • EBCDIC Transparency (#8030)
    • 120/144-Character Print Line (#5820 or #5821)
    • Multiple Record Transmission (#5010)
    • Synchronous Clock (#7705)

  3. 3770 Data Communication System. The 3770 Data Communications System (except 3777-2) with the non-programmable models of the 3771, 3773, 3774, 3775, 3776 and 3777-1 Communication Terminals (hereafter called 3770) can be connected to the central S/370 via a switched or nonswitched point-to-point communication line. The following features are required for operating a 3770 as an RSCS non-programmable terminal:
    • EBCDIC Transmission Code #9761
    • SDLC/BSC, Switch Control (#1460), or
    • BSC Point-to-Point (#1461)

  4. 3780 Data Communications Terminal. The 3780 Data Communications Terminal can be connected to the central S/370 via a switched or nonswitched point-to-point communication line. EBCDIC Transmission Code is required.

    The following devices and features are optional:

    • One 3781 Card Punch
    • Component Selection (#1601, required for the 3781)
    • EBCDIC Transparency (#3601)
    • Additional Print Positions (#5701)
    • Synchronous Clock (#7705)

  5. Programmable Terminals. Any processor now supported as a HASP workstation when programmed to run as a HASP workstation is supported as a workstation by the Spool MULTI-LEAVING (SML) support under RSCS. The DOS/VS Remote Job Entry Workstation Program (PRPQ WF0358) is also supported. Any processor running HASP, ASP, RES, JES2 and JES3 is supported as a main processor by RSCS when it itself assumes the role of a HASP programmable workstation. For specific configurations supported, refer to the HASP pages.

TRANSMISSION CONTROL UNITS SUPPORTED BY VM/370

  1. 2701 Data Adapter Unit:

    • For CPT-TWX (mdl 33/35) Line Control Type Terminals:

      • Telegraph Adapter Type II (#7885)

    • For 2770, 2780, 3270, 3770 (except 3777-2) as a 2770; 3776/3777-1 also as a 3780; 3777-2 as a S/360-20 MULTI-LEAVING Workstation) and 3780 Terminals:

      • Synchronous Data Adapter Type II (#7698)
        • EBCDIC Code #9060
        • EBCDIC Transparency (#8029)

    • For 1050 and 2741 Terminals:

      • Terminal Adapter Type I, mdl II (#4640)
        • Selective Speed (134.5 bps) #9581
        • 2741 Break Feature RPQ (M53193), and Break Command RPQ (858492)

    • As Needed:

      • Expanded Capability (#3815) - required if more than two low-speed adapters (either IBM Type I mdl II, or Telegraph Type II), or more than one high-speed adapter (Synchronous Data Adapter Type II), or one high-speed and at least one low-speed adapter are to be attached to the same 2701

      • Expansion Feature (#3855) - required for each line adapter after the first.

  2. 2702 Transmission Terminal

    • For 1050 and 2741 Terminals:

      • Terminal Control Base for IBM Terminal Control #9696

      • IBM Terminal Control Type I (#4615):
        • Selective Speed (134.5 bps) #9684
        • Type I Terminal Interrupt (#8200)
        • Data Set Line Adapter (#3233) and/or IBM Line Adapter (#4635) (4-wire)

    • For CPT-TWX (mdl 33/35) Line Control Type Terminals:

      • Terminal Control Base for Telegraph Terminal Control #9697

      • Telegraph Terminal Control Type II (#7912)
        • Pluggable End Characters** (return key generates an interrupt) RPQ (E62920)
        • Data Set Line Adapter (#3233)

      • Terminal Control Expansion (#7935) - required if both of the above terminal control bases are to be attached to the same 2702

    • As Needed:

      • 31-Line Expansion (#7955)

  3. 2703 Transmission Control Unit:

    • For 1050 and 2741 Terminals:

      • Start-Stop Base Type I (#7505) or Type II (#7506)

      • IBM Terminal Control Base (#4619)

      • IBM Terminal Control Type I (#4696):
        • Line Speed Option (134.5 bps) (#4878)
        • Type I Terminal Interrupt (#8200)
        • Data Line Set (#3205), and/or IBM Line Set 1B (#4687)

    • For CPT-TWX (mdl 33/35) Line Control Type Terminals:

      • Telegraph Terminal Control Base (#7905)

      • Telegraph Terminal Control Type II (#7912):
        • Line Speed Option (110 bps) (#4877)
        • Data Line Set (#3205)
        • Pluggable End Characters** (return key generates an interrupt) RPQ (E66707)

    • For 2770, 2780, 3270, 3777-2 (as a S/360-20 Multi-Leaving Workstation) and 3780 Terminals:

      • Synchronous Base (#7703, #7704 or #7706)

      • Synchronous Terminal Control for EBCDIC (#7715):
        • Transparency #9100
        • Synchronous Line Set (#7710)

    • As Needed:

      • Base Expansion (#1440) - required if more than one base type is to be attached to the same 2703

  4. Integrated Communications Adapter (ICA) (#4640) (available on the S/370 mdl 135, 135-3, 138)

      • Additional Lines (#4722-#4728)

    • For 1050, 2741, 3767 (as a 2741) and 5100 (as a 2741) Terminals:

      • Terminal Adapter Type I mdl II #9721-#9728
        • Switched Network Facility #9625, #9632 (optional)
        • Write Interrupt #9745, #9752
        • Read Interrupt #9737, #9744
        • Unit Exception Suppression #9729, #9730 (optional)

    • For the 3767 only (as a 2741):
        • 200 bps (#2711-#2718), or
        • 300 bps #9593, #9600

    • For the 5100 only (as a 2741):
        • 300 bps #9593, #9600

    • For 2770, 2780, 3270, 3770 (except 3777-2) as a 2770; 3776/3777-1 also as a 3780; 3777-2 (as a S/360-20) and 3780 Terminals:

      • Synchronous Data Adapter Type II #9649, #9656
        • Half-Duplex Facility #9617, #9624
        • EBCDIC Transparency #9673, #9680)

    • For CPT-TWX (mdl 33/35) Line Control Type Terminals:

      • Telegraph Adapter Type II #9785, #9792

      • Switched Network Facility #9625, #9632

  5. 3704/3705-I/3705-II Communications Controller

    See the 3704/3705-I/3705-II machine pages for required feature codes.

  6. 4331 Communications Adapter

    See the 4321 or 4331 machine pages for required feature codes.

    Note: CPT-TWX (mdl 33/35) terminals or equivalent devices are supported only at 110 bps by the 3704/3705 Network Control Program under VM/370.

    ** Although not required, these features enhance the usability of these terminals.

Two-Channel Switches

VM/370 has Alternate Path Support and does not take advantage of the Two-Channel Switch, and Two-Channel Switch, Add'l features.

Dedicated Devices

With VM/370 Release 2 and 3, any input/output device not supported by VM/370 but which is attachable to an IBM S/370 and conforms to S/370 architecture may be eligible for dedicated use by a virtual machine under VM/370. The subclass of the device should be specified during VM/370 system generation so that virtual CCW strings directed to the unsupported device will be translated correctly; refer to the "VM/370: Planning and System Generation Guide", GC20-1801, for details. The standard device and program restrictions also contained in that publication must be observed. The device must be tested in this environment to ensure proper operation.


CONFIGURATIONS SUPPORTED BY CMS

  • Virtual storage size: Recommended minimum of 320K bytes up to 16 million bytes in multiples of 4,096 bytes.

  • Virtual console - any terminal supported by VM/370 as a virtual machine operator's console.

  • Any virtual card readers, card punches (except the 2520) and printers supported by VM/370 as spooling devices.

  • Up to ten virtual 2314, 2319, 3330, 3333, 3340, 3344 or 3350 direct access storage devices as well as the 3850 Mass Storage System 3330V volumes as 3330s. Each virtual disk is at minimum one cylinder. The CMS file system constrains virtual disk sizes as follows: A maximum of 115 cylinders on each virtual 3350 in native mode, a maximum of 246 cylinders on each virtual 3330 or 3333, a maximum of 348 cylinders on each virtual 35Mb 3340, and a maximum of 682 cylinders on each virtual 70Mb 3340. Note that OS and DOS virtual disks read by CMS are not constrained by these limits. The CMS system disk is required and reduces the number of user disks online at any given time to nine.

  • Up to four 2400, 2415, 2420 or 3420 (7- or 9-track), or 3410 (9-track only) Magnetic Tape Units.

MINIMUM VM/370 CONFIGURATION

  • One of the S/370 Processors previously designated with at least 393,216 bytes of real main storage
  • One Console
  • One Printer
  • One Card Reader*
  • One Card Punch*
  • Two Spindles of Direct Access Storage
  • One 9-track Magnetic Tape Unit
  • One Transmission Control Unit (or the Integrated Communications Adapter on the S/370 mdl 135, 135-3, 138); if only local 3277 Display Stations are used as terminals, then only a 3272 Control Unit is required
  • One Multiplexer Channel**
  • One Selector or Block Multiplexer Channel**
  • One Communication Terminal

    * Not required if support for a cardless VM/370 system is used.

    ** A Multiplexer, Selector or Block Multiplexer Channel is not required on those processors (e.g., the 4331 Processor) that support integrated adapters.

The requirement for at least one transmission control unit, line and remote terminal can be eliminated if the customer plans to run only two virtual machines using the primary and alternate system consoles. The requirement is also eliminated if the only terminals to be used are 3277 Display Stations attached to a 3272 Control Unit. These conditions permit a customer to install VM/370 earlier and gain experience with multiple concurrent virtual machine operation and/or CMS time sharing before the installation of his teleprocessing terminals, control units and lines.

VM/370 requires a minimum of 384K bytes of accessible main storage. This storage size will support a mixed-mode environment, that is, CMS running concurrently with another virtual machine. A minimum 384K system provides limited performance capability. Therefore, installation of VM/370 for mixed mode environment in an already installed S/370 should consider at least a main storage upgrade.

VM/370 supports a cardless environment. By using the facility to spool accounting records in VM/Basic System Extensions or VM/System Extensions and altering the system generation procedures to use tape devices, the need for a card reader/punch can be eliminated. This capability requires the installation of either VM/Basic System Extensions program product (5748-XX8) or the VM/System Extensions program product (5748-XE1). Further information is contained in the "VM/370 Planning and System Generation Guide" (see updates SN25-0499 and SN25-0757). Specific details relevant to the minimum configuration required for hardware maintenance should be directed to the NSD Division.


REPRESENTATIVE VM/370 CONFIGURATION

  • 3145 512K storage
  • 3215 Console Printer-Keyboard
  • 1403 Printer mdl N1 (two)
  • 3330 or 3340 DASD drives as needed to meet the requirements of VM/370, the virtual machine operating systems and the users
  • 3420 Magnetic Tape Units (two)
  • 2540 Card Read Punch
  • 3704 Communications Controller
  • 3277 Display Stations, as needed with the 3271 or 3272 Control Unit
  • 2741 or Communication Terminals (as needed)
  • 3232-51 Keyboard Printer
  • 3767 Communication Terminals (as 2741s) (as needed)
  • Two Block multiplexer channels (#1421, #1422) with Word Buffer feature (#8810)
  • One Multiplexer channel
  • 6733 Typewriter Communication Module with Electronic Typewriter 85 (as needed) as a CPT-TWX 33/35

CUSTOMER ENGINEERING CONSIDERATIONS

Engineering Change Levels

For a listing of engineering change (EC) levels at which the operation of VM/370 has been verified, refer to "VM/370: Release 2 Guide" (GC20-1815).

UCW CONSIDERATIONS

It is essential to the operation of VM/370 that sufficient Unit Control Words (UCWs) are installed for the S/370 mdl 135, 135-3, 138, 145, 145-3, 148, 155II or 158 multiplexer channel. Before ordering, contact your local NSD Installation Planning Representative for assistance in determining the necessary quantity of UCWs for your configuration. Installation options controlling the use of UCWs should be carefully reviewed with NSD prior to installing VM/370 on any S/370.


RELIABILITY, AVAILABILITY AND SERVICEABILITY

The VM/370 system is based on the proven concepts of the CP-67/CMS system which has been in use by customers since 1968. VM/370 utilizes S/370 architecture, including RMS, to enhance its own reliability, availability and serviceability (RAS). The environment of multiple concurrent virtual machines may result in improved RAS for many S/360 operating systems that are run under VM/370.

The VM/370 features that improve reliability are:

  • User isolation, each in his own virtual machine.

  • Read-only protection of shared or critical disks.

  • Restricting access to other users' disks via password protection.

  • Screening of all interrupts by the control program to prevent abnormal termination of OS due to receiving I/O interrupts from devices not included in the OS nucleus.

  • Nucleus protection in CMS.

Availability is enhanced for the following reasons:

  • VM/370 allows users to run concurrently as many versions, levels, types and copies of operating systems as they require.

  • Customers can generate, update and test operating systems without the need for a dedicated machine. Premature conversion of a customer's production work to an insufficiently tested new environment can be avoided.

  • When the control program detects a permanent storage error in a main storage page frame that is being used by a virtual machine, the frame will be marked unusable. If the page frame has not been altered by the virtual machine, a new page frame is assigned to the virtual machine and a fresh copy of the page is brought in the next time the page is referenced.

    The storage error is transparent to the virtual machine user. If the frame has been altered, VM/370 resets the virtual machine, clears its virtual storage to zeros and sends an appropriate message to the user. Normal system operation continues for all other users.

  • If, in writing out a page on the paging device, the control program encounters a defective area on the disk, that area is marked as unusable and the page is written elsewhere on the paging device.

  • Upon abnormal termination, the control program will automatically dump and reload itself without system operator intervention. Completed spool files will be saved, and communication lines will be re-initialized following the reload. Each user can then re-initialize his virtual machine.

  • When a terminal or line error is detected for a virtual machine operator's console, VM/370 breaks connection with that user. However, that user is not logged off by VM/370 for 15 more minutes, giving him that period of time to attempt to re-establish connection with the system for that virtual machine.

Serviceability is improved by:

  • Providing various commands to trace, examine and alter the operation of a virtual machine.

  • Providing IPCS commands and facilities which analyze CP abend dumps, generate user-detected problem reports, allow viewing of disk-resident CP abend dumps and allow management of problems and their status.

  • Recording on the VM/370 system residence disk machine checks, channel checks and I/O errors for CE use. The above data can be printed by running the appropriate VM/370 service programs in a virtual machine.

  • Allowing a Customer Engineer to run, concurrently with customer production, any of his system-supported and stand-alone diagnostics that avoid the VM/370 restrictions stated in the "IBM Virtual Machine Facility/370: Planning and System Generation Guide" (GC20-1801).

Serviceability of the 3704/3705 Under VM/370

VM/370 provides a concurrent problem determination capability for use with the 3704/3705 as a function of the NETWORK TRACE command. Options to this command allow tracing each basic transmission unit sent to and received from the 3704/3705 and also activating the network control program line trace for a particular 3704/3705 resource. For details on the NETWORK TRACE command, refer to "VM/370: Operator's Guide" (GC20-1806).

VM/370 utilizes the Online Test Stand-alone Executive Program (OLTSEP) at the primary interface for diagnostic online tests (OLTs) for all devices attached to the system. This means of support restricts the function of diagnostic tests that are provided for the 3704/3705 in network control mode when used by VM/370 for control of virtual machine operators' consoles. The following defines the serviceability aids that are or are not available for the 3704/3705 when used in this manner.

3704/3705 Internal Function Tests (IFTs): IFTS run under OLTSEP and provide the full level of device serviceability in this mode of operation that is available for the 3704/3705. An IFT requires the entire 3704/3705 for its use. The 3704/3705 is therefore not available for normal system use.

Down-Line Tests:

  • Terminal Tests - The 3700 series Online Terminal Test (OLTT) programs that are required to maintain the terminals supported by VM/370 through the Network Control Program will function under OLTSEP. This mode of operation will require the dedication of the 3704/3705 to the OLTSEP virtual machine, and therefore, the 3704/3705 cannot be used for normal system operations for the duration of the test.

  • Line/Modem Tests - The 3700 series Online Terminal Test (OLTT) programs do not function under OLTSEP. The 2700 series OLT programs can be executed under OLTSEP if the line or lines to be tested are partitioned emulation lines, and are set to emulation mode. The 2700 series OLTs are terminal tests that are also able to aid in line error detection.

Additional terminal serviceability aids and line problem determination aids are provided for the Network Control Program by the 3704/3705 Control Panel Tests, as outlined in the "IBM 3704 and 3705 Communications Controller Operator's Guide" (GA27-3055) and the VM/370 ECHO command as defined in the "VM/370: Command Language Reference for General Users" (GC20-1820).


SECURITY AND AUDITABILITY

Since the virtual machines created by VM/370 are essentially equivalent to stand-alone S/370 machines, the isolation between virtual machine programs approaches the isolation between physically separate systems. This same isolation protects the VM/370 Control Program (CP) from inadvertent or malicious modification, thus protecting the protection mechanisms. Some of the security features provided are as follows:

  • Main storage isolation - Virtual machine is restricted to its own address space; shared storage (if any) is enforced read-only.

  • CP privilege classes restrict usage of the sensitive CP facilities to installation-authorized virtual machines.

  • Password protection is provided both for access to the CP system and for access to user DASD files.

  • Installation exits are provided to allow for extension of the access restrictions or for implementation of access journaling.

  • Built-in traps prevent password penetration through repetition of access attempts.

  • All virtual machine I/O is monitored and checked against extent authorization controls in the virtual configuration.

An additional security-related feature of VM/370 is that explicit installation action is required to permit the VM Measurement Facility to monitor potentially sensitive data transmitted to/from each user terminal.


PERFORMANCE

VM/370 has been designed to handle a diverse set of requirements with virtual machines.

The performance of systems and programs running in virtual machines, as compared to real machines, will be reduced by varying degrees. Thus, performance will be influenced by such factors as: The total amount of real storage available; the speed, capacity, and number of paging devices; CCW translation, privileged instruction and I/O interrupt handling for virtual machines; and the use of CP performance options.

Because of the dynamic nature of the virtual machine environment, no specific statement can be made concerning general performance. However, it can be said that VM/370 gives highest priority to the interactive users for short periods of time, while the heavy computing user will be given less frequent but longer periods of use.

VM/370 system performance data is obtainable by users both at the console and, in an extended form, through a general-purpose data collection and recording facility with the VM/370 Measurement Facility, as follows: Data obtainable at the console will show current load conditions on the system. Information on utilization and contention for major system resources (Processor, real storage and devices) will allow the system analyst to identify possible bottleneck conditions.

The data collection and recording facility can record a wide range of performance related statistical data for more detailed information. Several classes of data collection are provided which may be activated either separately or together. The accumulated data is recorded on tape for later examination and reduction by the user.

The 3270 remote and binary-synchronous line configurations affect response times observed at the 3270 remote display devices. On the basis of the speed of the communication line, users of the CMS Editor may choose between multiple line transmission to the 3270 device (similar to CMS editor support for local 3270s) and a single line at a time mode (as though the display screen were a 2741).

To assist you in evaluating your customer's environment while running under VM/370, a performance guideline, "Introduction to Systems Performance Evaluation, Virtual Storage Systems" (ZZ20-2349) is available from Mechanicsburg. Considerations regarding performance can also be found in the "IBM VM/370: Introduction" (GC20-1800), "Virtual Machine Operating System" section and in the "VM/370: System Programmer's Guide" (GC20-1807). Detailed VM/370 performance information concerning machine configurations and varying combinations of CMS users, batch, and/or multiple batch virtual machines are available at your local Market Support Center.


INSTALLATION PLANNING

Generating and installing the initial release of VM/370 requires coordinated planning between the customer, DP marketing representative, systems engineers (providing marketing support services), NSD programming and service representatives and the communications common carrier. The "IBM Virtual Machine Facility/370: Planning and System Generation Guide" (GC20-1801) should be reviewed thoroughly before ordering or generating the VM/370 system.


PROGRAMMING UPDATE SERVICE

Programming update service for VM/370 is provided using the VM/370 Program Level Change (PLC) service.

A given release of VM/370 consists of the release base as well as all updates made available to date via the VM/370 PLC service. The release is designated by both the base number and the PLC number. Support for a given release of VM/370 will be available for six months following the next subsequent release of VM/370. PLCs issued to distribute fixes to an old base, after a new base is released, do not constitute a new release of the system.

The VM/370 PLC is a system update service that can include new functions as well as cumulative system changes. The latest PLC tape is made available at ISD as well as all previous updates since the last VM/370 release base. NSD is responsible for initially ordering the PLC service. Thereafter, ISD will automatically ship the PLC tapes to the NSD location, and NSD is responsible for applying the updates to the user's system. These tapes are not automatically distributed to customers of record by ISD.

The VM/370 PLC Service is ordered by the NSD Branch Office using Program Order Form Z120-1957 and specifying 370 VPLC. Refer to General PSM Number 23 for instructions in filling out the form.


PUBLICATIONS

  • SY-0886 VM/370 System Logic and Problem Determination Guide Vol. 1 Control Program (CP)
  • SY-0887 VM/370 System Logic and Problem Determination Guide Vol 2. Conversational Monitor System (CMS)
  • SY-0888 VM/370 System Logic and Problem Determination Guide Vol 3 Remote Spooling Communications System (RSCS)
  • GC20-1801 VM/370 Planning and System Generation Guide
  • GC20-1806 VM/370 Operator's Guide
  • GC20-1807 VM/370 System Programmer's Guide
  • GC20-1808 VM/370 System Messages
  • GC20-1810 VM/370 Terminal User's Guide
  • GC20-1816 VM/370 RSCS User's Guide
  • GC20-1818 VM/370 CMS Command and Macro Reference
  • GC20-1819 VM/370 CMS User's Guide
  • GC20-1820 VM/370 CP Command Reference for General Users
  • GC20-1834 VM/370 Release 6 Guide
  • GC20-1823 VM/370 Interactive Problem Control System User's Guide
  • GC33-4021 OS/VS and "VM/370 Assembler Programmer's Guide
  • GC20-1800 VM/370 Introduction
  • GC20-1809 VM/370 OLTSEP and Error Recording Guide
  • GC20-1813 VM/370 Glossary and Master Index
  • GC20-1821 VM/370 Operating Systems in a Virtual Machine
  • GX20-1826 VM/370 Quick Guide for Users (Reference Summary)
  • GX20-1961 VM/370 Summary of VM/370 CP and CMS Commands reference card)
  • SY20-0882 VM/370 Service Routines Program Logic
  • SY20-0884 VM/370 Data Areas and Control Block Logic
  • SYB0-0900 VM/370 Control Program Listings Microfiche
  • SYB0-0901 VM/370 Conversational Monitor System Listings Microfiche
  • SYC0-9000 VM/370 Remote Spooling Communications Subsystem Microfiche
  • SYC0-9001 VM/370 Interactive Problem Control System Microfiche
  • SJD2-4350 VS2 EREP Microfiche
  • GC29-8300 VM/370 Environmental Recording, Editing and Printing (EREP) Program
  • SY25-7701 VM/370 Environmental Recording, Editing and Printing (EREP) Program Logic
  • GC33-4010 OS/VS, DOS/VS and VM/370 Assembler Language
  • SY33-8041 OS/VS and VM/370 Assembler Logic

SCP PROGRAMMING SERVICES: Class 1 SCP