5685-001 IBM Enterprise Systems Architecture/370 and MVS/System Product-JES2 Version 3


Table of Contents

5685-001 IBM Enterprise Systems Architecture/370 and MVS/System Product-JES2 Version 3
IBM U.S. Product Life Cycle Dates
Program Number
Abstract
Product Positioning
Highlights
Description
Technical Description

  • Operating Environment
  • Hardware Requirements
  • Software Requirements
  • Planning Information
    Security, Auditability, and Control
    5685-001 MVS System Product JES2 Version 3 Release 1.3
    Program Number
    Abstract
    Highlights
    Description
    Operating Environment
    Compatibility
    Performance Considerations
    Security, Auditability, and Control
    5685-002 MVS/System Product-JES3 Version 3 Releases 1.1 and 1.2
    Abstract
    Highlights
    Description
    Operating Environment
    Compatibility
    Performance Considerations
    Security, Auditability, and Control
    Publications
    5685-001 MVS/System Product-JES2 Version 3 Release 1.1
    Abstract
    Highlights
    Description
    Operating Environment
    Compatibility
    Performance Considerations
    Security, Auditability, and Control
    Publications
    5685-001 MVS/System Product-JES2 Version 3 Release 1.0
    Program Number
    Abstract
    Highlights
    Description
    Operating Environment
    Compatibility
    Security, Auditability, and Control
    Publications

    5685-001 IBM Enterprise Systems Architecture/370 and MVS/System Product-JES2 Version 3


    IBM U.S. Product Life Cycle Dates

    
    Program                                  Marketing   Service      Replaced
    Number   VRM     Announced   Available   Withdrawn   Discontinued    By
    

    5685-001 3.02.2 1990/09/05 1990/09/05 1993/09/30 1997/03/31 5695-047 5685-001 3.01.3 1990/01/23 1990/02/23 1993/09/30 1997/03/31 5695-047 5685-001 3.01.1 1988/12/06 1988/12/30 1993/09/30 1997/03/31 5695-047 5685-001 3.01.0 1988/11/15 1988/11/23 1993/09/30 1997/03/31 5695-047


    Program Number

    • 5685-001 MVS/SP-JES2 Version 3
    • 5685-002 MVS/SP-JES3 Version 3

    Abstract

    There is more than one description of this product.

    (For IBM US, No Longer Available as of September 30, 1993)

    (For IBM US, Program Services Discontinued as of March 31, 1997)

    MVS/System Product V3 supports the Enterprise Systems Architecture/370 (ESA/370*) and provides significant new base control program (BCP) function and system services. MVS/SP* V3 provides a vehicle for I/O reduction and dramatically increases the virtual storage addressable by an application by allowing access to multiple data-only spaces. MVS/SP V3 provides improved RAS by allowing programs to be isolated from data.

    MVS/SP V3 can be used on the 3090* Enhanced Models and 4381 Model Groups 91E and 92E.


    Product Positioning

    Not available.


    Highlights

    • New processor architecture

    • Enhanced data handling capabilities

    • Increased addressability

    • Improved software RAS

    • Enhanced services for application development

    Description

    MVS/SP V3 supports and utilizes the Enterprise Systems Architecture/370* by providing enhancements to BCP function which, when used, can enable a significant reduction in input/output processing delays. New system services provide:

    • Increased addressability and improved RAS by allowing data to be separated from programs in data-only spaces called data spaces. 370-XA instructions that address virtual storage can be used to operate on data in a data space.

    • Faster access to data since new system services use data spaces to reduce the number of I/O operations to DASD. These services can be used to enhance the performance of user applications.

    • Improved installation management through a system service which maintains in-storage directory entries and retrieves modules from data spaces.

    MVS/SP V3 provides continued bi-modal support and compatibility with previous versions of MVS/System Product.

    MVS/ESA:

    MVS/ESA* is comprised of MVS/SP V3 and MVS/DFP* V3. MVS/ESA is the primary delivery vehicle for future MVS and DFP functional enhancements and constraint relief.

    Enterprise Systems Architecture/370:

    Enterprise Systems Architecture/370 is an evolutionary step beyond 370-Extended Architecture. It is designed to broaden an installation's choice of functions available for the development of new applications. Utilization of the architecture allows a reduction of the effort required for activities such as managing large data sets or multiple small data sets. Enterprise Systems Architecture/370 also removes certain constraints in the 370-Extended Architecture that are limiting today's applications. New hardware addressing support allows accessing of virtual storage in multiple address spaces and data spaces. This significantly extends addressability for system, subsystem, and application functions that utilize ESA/370.

    Enterprise Systems Architecture/370 is a new architecture unique to the 3090 Enhanced Models and 4381 Model Groups 91E and 92E.

    Support for Enterprise Systems Architecture/370:

    MVS/SP V3 expands addressing capabilities, simplifies operations, provides constraint relief, and improves the RAS characteristics of MVS.

    MVS/SP V3 uses ESA/370 and also provides a base for IBM subsystems and user applications to take advantage of the extensions. While offering significantly extended addressability through access to multiple address spaces and data spaces, MVS/SP V3 is compatible with existing 24-bit and 31-bit subsystems, user applications, and external interfaces.

    Following are the Key Features of MVS/SP V3:

    Data Spaces:

    MVS/SP V3 allows the creation of data-only spaces referred to as data spaces. Because access to a data space is controlled by hardware, data spaces enhance data isolation as well as extend addressability. Within a data space, all addresses are contiguous and available to the application because the virtual storage is not divided into a system and private area, as in an address space. Application programs can use data spaces directly, and data in virtual processing is extended to allow users to map data in virtual objects into a data space, as well as into an address space.

    Subsystems and user applications can have simultaneous access to multiple address spaces, multiple data spaces, or both. Each address space can contain up to two gigabytes of code and data. Each data space can contain up to two gigabytes of data.

    Appropriate controls for data spaces are provided for installation management.

    Hiperspaces:

    A high performance space (Hiperspace*) is designed exclusively for "reading" and "writing" blocks of data in 4K multiples. Data may be "read" from a Hiperspace to an address space or 'written' from an address space to a Hiperspace using new system services. Through efficient use of the storage hierarchy, use of Hiperspaces can provide better response time for user requests. Hiperspaces never reside in central storage.

    There are two types of Hiperspaces. The first can be viewed as a high-speed storage device and can be accessed only by authorized programs. This type of Hiperspace can only be used on processors with expanded storage. While data in a data space can reside anywhere in processor storage or on auxiliary storage and is subject to normal storage contention and paging activity, the data in the first type of Hiperspace will reside only in expanded storage.

    The second type of Hiperspace, which will reside in expanded storage, if available, and can be backed by auxiliary storage, is available to all applications and can be referenced from high level Languages through the new data windowing services described in the next section. Maximum benefit is obtained if most of the accesses are to data in expanded storage.

    System Services:

    • Data windowing services allow high level language applications to access and scroll through large permanent data objects (data in virtual) and/or large temporary data objects. This data is seen through virtual storage windows in an application program. A window is a user-defined area (in the application) that maps portions of the data object.

      Data windowing services support calls from FORTRAN, PL/I, COBOL, C, and Pascal, as well as from Assembler language programs. Standard high level Language or Assembler statements are used to manipulate data in the window.

    • An authorized service allows programs to store objects (such as load modules) in data spaces for the use of system, subsystem, or application functions. Because these objects would, otherwise, reside on I/O devices, this service provides improved response time by reducing the number of I/O operations required to access the objects.

    • A library service is provided that dynamically identifies the system's most active production load modules and places them in a data space for subsequent retrieval. This service also maintains and controls in-storage directories of production libraries for non-program libraries, as well as program libraries. These in-storage directory entries can be selectively refreshed. This service reduces the I/O load resulting from repeatedly fetching active modules from DASD and eliminates directory search I/O for production library directories.

    Systems Application Architecture (SAA):

    MVS/ESA will be the primary base for future SAA enhancements in the MVS environment.

    Refer to "Systems Application Architecture: An Overview" (GC26-4341) for details.


    Technical Description

    Operating Environment

    Hardware Requirements

    MVS/SP V3 requires a 3090 Enhanced Model at the appropriate EC level that supports the Enterprise Systems Architecture/370 or a 4381 Model Group 91E or 92E processor.

    MVS/SP V3 continues to support I/O devices supported on previous MVS/XA systems, with the exception of System/3 or 1130 operating as a JES2 remote work station.

    MVS/SP V3 requires a minimum real storage configuration of 8MB.

    Software Requirements

    • The JES2 component shipped with MVS/SP V3 is functionally equivalent to that shipped with MVS/SP-JES2 2.2.0 (FMID: HJE2221).

      For migration purposes, the following JES2 component levels will also be supported:

      • JES2 component shipped with MVS/SP 1.3.6 (FMID: HJE1367)
      • JES2 component shipped with MVS/SP 2.1.5 (FMID: HJE2215)

    • The JES3 component shipped with MVS/SP V3 is functionally equivalent to that shipped with MVS/SP-JES3 2.2.1 (FMID: HJS2220).

      For migration purposes, the following JES3 component levels (with or without the JES3 SNA/NJE Enhancement) will also be supported:

      • JES3 component shipped with MVS/SP 1.3.4 (FMID: HJS2329)
      • JES3 component shipped with MVS/SP 2.1.5 (FMID: HJS2215)

    • Assembler H V2 (5668-962) with a PTF is required.

    • SMP/E Release 4 (5668-949) is required for installation and maintenance.

    • Either MVS/XA DFP 2.3 (5665-XA2) or MVS/DFP V3 (5665-XA3) is required.

      The Data Facility Storage Management Subsystem* has been designed for use in an operating environment that supports Enterprise Systems Architecture/370.

      MVS/SP-JES2 V2 support will begin controlled introduction in 3Q89 to accommodate the Storage Management Subsystem functions of MVS/DFP V3 in the MVS/XA environment. This support, however, will not provide the function and performance enhancements available in MVS/SP V3.

      JES3 support for the Storage Management Subsystem functions of MVS/DFP V3 will be provided with a new MVS/SP-JES3 V3 component, to begin controlled introduction in June, 1989.

    Additional information on programming requirements will be available prior to general availability.


    Planning Information

    Customer Responsibilities

    Installation Considerations:

    System generation requirements for the installation of MVS/SP V3 and Data Facility Product (DFP) vary due to the possible combinations of base systems used for the installation. The MVS/SP V3 program directory contains specific installation instructions.

    The following should be evaluated when migrating to MVS/SP V3 in environments requiring that more than one version of MVS be run on the same processor:

    1. The 3090 Processor Resource/Systems Manager Feature, available on all 3090 Enhanced Models August 1988.

    2. VM/XA System Product (VM/XA SP) with a programming enhancement to the latest release, available December, 1988. This support is for guest operating systems utilizing the ESA/370. No native VM support is provided.

    Migration Considerations:

    To ease migration to MVS/SP V3, has authorized the use of the components and macros (migration aids) listed below on a processor running MVS/370 or MVS/XA in a location(a) where MVS/SP V3 and DFP are licensed. Use of these migration aids is permitted on another processor executing MVS/SP V1 or MVS/SP V2 in the location for a period of 18 months after shipment from of the first MVS/SP V3 and DFP programs for the location.

    • Linkage Editor provided with DFP
    • MVS/ESA SYS1.MACLIB
    • MVS Configuration Program

    Note (a): The term "location" is defined in the "Agreement for Licensed Programs" (Z125-3358).

    The linkage editor provided with MVS/370 Data Facility Product (5665-295) is equivalent to the linkage editor provided with MVS/XA Data Facility Product (5665-284 or 5665-XA2) or MVS/Data Facility Product V3 (5665-XA3). The user with MVS/370 DFP installed need not replace the linkage editor with the one provided with MVS/XA DFP or MVS/DFP.

    A procedure for adding this linkage editor to an MVS/370 system without MVS/370 DFP installed is provided in the MVS/XA DFP or MVS/DFP program directory. A new system library, SYS1.MIGLIB can be used to process dumps with IPCS MVS/SP V3 on previous levels of MVS/XA (but not on MVS/370).

    The MVSCP available with MVS/SP V3 or subsequent releases will execute on MVS/370 or MVS/XA. The output of this program is required in order to IPL MVS/SP V3 or subsequent releases.

    Performance Considerations

    Measurements and analysis indicate the performance of MVS/SP V3 when compared to MVS/SP V2 run on ESA/370 supported hardware will be in the range of -3 to +12 per cent. The low end of the range is in the dedicated commercial batch environment on uniprocessors, while the greatest improvement is in the IMS environment running on large multi- processors. In addition, system response time improvements through I/O reduction can be obtained by use of data spaces, Hiperspaces and other MVS/SP V3 system services. Detailed performance information will be available in a Washington Systems Center Technical Bulletin prior to September 30, 1988.


    Security, Auditability, and Control

    Data security and auditability in the environment created by MVS/SP V3 are enhanced by the functions available in the Resource Access Control Facility (RACF) Version 1 Release 8 licensed program (5740-XXH).

    RACF provides security and protection of software resources for those installations requiring it. RACF can be used to ensure that access to data (and optionally other resources) is authorized according to the installation's established controls.

    User management is responsible for the evaluation, selection and implementation of such features, for administrative procedures and for appropriate controls in application systems.

    If sensitive data is sent over external communication facilities, user management may wish to pursue the application of cryptography.


    5685-001 MVS System Product JES2 Version 3 Release 1.3


    Program Number

    • 5685-001 MVS/SP-JES2 Version 3 Release 1.3
    • 5685-002 MVS/SP-JES3 Version 3 Release 1.3

    Abstract

    IBM MVS/ESA MVS/System Product JES2 Version 3 Release 1.3 and IBM MVS/ESA MVS/System Product JES3 Version 3 Release 1.3 reduce elapsed time for batch job streams that access the same VSAM and QSAM data sets. MVS/SP 3.1.3 is part of a Trusted Computer Base to be evaluated at the B1 level by the National Computer Security Center (NCSC) of the U.S. Department of Defense. These enhancements also provide additional security function for the commercial environment. MVS/SP 3.1.3 also removes constraints to application growth, improves system management, and provides enhancements for applications.


    Highlights

    • Reduction in elapsed time for batch job streams accessing the same data sets
    • System security enhancements
    • Performance enhancements for the base control program and JES3
    • Relief for virtual storage constraints to application growth
    • Improved system management
    • Enhancements for applications: time requests and virtual storage management
    • Enhanced printer support for JES2.

    Description

    Elapsed Time Reduction for Batch Jobs:

    MVS/SP 3.1.3 reduces I/O for batch jobs in two separate functions, Hiperbatch* and batch local shared resources (LSR).

    Hiperbatch, a new MVS/ESA function, can reduce the execution time of certain batch job streams that access the same VSAM and QSAM data sets. Hiperbatch stores VSAM and QSAM data in Hiperspaces for access by multiple jobs.

    Once the data resides in a Hiperspace, VSAM and QSAM application programs can access the data without actual I/O operations, thus reducing the elapsed time for the application programs in systems that are not constrained for expanded storage, with applications that share the same VSAM or QSAM data sets.

    Hiperbatch can relieve DASD constraints when multiple jobs read the same VSAM or QSAM data set. This eases I/O tuning.

    A customer should not need to rewrite application programs or JCL to use Hiperbatch.

    Batch LSR assists batch applications that randomly access VSAM data sets. An installation can switch an application from using VSAM non- shared resources (NSR) to using VSAM local shared resources (LSR). The switch is accomplished without changing the application or link-editing it again; only JCL changes are required.

    Note: Batch LSR enables programs written in high-level languages to use LSR without the need for coding assembler language subroutines. Batch LSR is available through the service process as APAR OY24097.

    System Security Enhancements:

    MVS/System Product Version 3 Release 1.3 provides a number of functions for enhancing system security for the commercial environment. MVS/SP 3.1.3 is part of a Trusted Computer Base, to be evaluated at the B1 level by the National Computer Security Center (NCSC) of the U.S. Department of Defense. Only a subset of available security-related functions must be activated for a system designed to meet B1 criteria; an installation can select individual functions to customize its security, depending upon installation security requirements.

    The following security enhancements are available to MVS/SP Version 3 Release 1.3 when Resource Access Control Facility Version 1 Release 9 (RACF 1.9), and JES2 Version 3 Release 1.3 or JES3 Version 3 Release 1.3 are also installed.

    • Operator Identification and Authentication: This enhancement enables an installation to identify system operators and their associated IDs, passwords, and security labels.

    • Operator Command Authorization and Auditing: An installation can selectively permit the use of commands by operator as well as by console and can audit command activity in a variety of ways and from a variety of sources, including from remote job entry (RJE) and network job entry (NJE).

    • Device-Level Access Control: A customer can determine if unit record devices, teleprocessing or communications devices, and graphic devices should be allocated.

    • Enhanced Auditing Capability: New and changed system management facility (SMF) records provide increased auditing capabilities. To prevent loss of audit records, the system notifies operators when SMF data sets are becoming full.

    • Increased Security for Job Entry Environments: JES offers increased security with access control for job input sources (including RJE and NJE), SYSIN and SYSOUT data sets, and printers.

    • Enhanced NJE Security: NJE provides security validation or auditing functions in a JES NJE environment. They include:

      • Enhanced auditing and restricting of resources on a JES node basis

      • Authorizing and auditing all work (jobs and SYSOUT) entering or leaving a node

      • Propagating the security information associated with jobs and SYSOUT. This additional information is used to validate a request for resources.

      • Encrypting passwords for jobs sent through a network

    • Enhanced RJE Security: RJE provides remote sign-on validation through RACF in a JES RJE/RJP environment.

    • Adaptability of Security Processing: JES provides new installation exit points for modifying or enhancing system authorization facility (SAF) processing and RACF auditing.

    Performance Enhancements:

    • SMF Enhancements: SMF now allows an installation to change the control interval size of the SMF data sets. Thus, the installation can increase the value to improve the rate of throughput. The enhancements are available through the service process as APAR OY19682.

    • JES3 General Service Routines: The processing for JES3 timer services, JES3 multifunction monitor, and JES3 trace routines has been changed to improve JES3's performance.

    • JES3 Setup Processing: Improvements in JES3 have reduced the amount of spool input/output and CPU usage in JES3 setup processing.

    Virtual Storage Constraint Relief:

    • SMF Enhancements: SMF enhancements can ease virtual storage constraints by using storage above 16 megabytes.

    • Virtual Storage Constraint Relief: MVS/SP 3.1.3 can relieve virtual storage constraints by allowing programs that use VSAM data sets to request that the VSAM control blocks be placed above 16 megabytes. This change was released 2/89 through the service process and is included in MVS/SP 3.1.3.

    System Management Improvements:

    • SMF Enhancements: SMF changes help prevent loss of the system and job-related data that SMF collects. The changes include a new interactive problem control system (IPCS) subcommand to obtain SMF data from a dump.

    • Large Job Management Improvements: MVS/SP 3.1.3 improves the management of large jobs by handling central storage more efficiently. With the improvement, the system provides more frames of central storage by trimming large jobs in stages. The system performs physical swaps of large jobs only if trimming the swap-set for the jobs does not produce the needed frames.

    • LLA Enhancements: A new macro allows authorized programs to refresh the LLA directory. Subsystems that manage their own partitioned data set (PDS) directory entries can use this macro to keep the LLA directory equivalent, so the subsystem can fetch modules quickly from the LLA VLF data space.

      Changes in the LLA staging algorithm result in a better selection of modules in the LLA virtual lookaside facility (VLF) data space.

    • Common Area Data Space: A common area data space (CADS) enables MVS/SP 3.1.3 components and subsystems to exploit access registers and data spaces by offering additional function, providing common area virtual storage constraint relief, and easing customer use of access registers. CADS is available through the service process as APARs OY20822, OY20849, and OY20854.

    Enhancements for Applications:

    • Time Requests: An application program can request the CPU time or vector time used by a task. Previously, only the CPU time was available and only for authorized programs.

    • Virtual Storage Management: New callable service requests allow applications to manage virtual storage that the applications obtain in address spaces and data spaces. The applications use the services to divide the virtual storage into cell pools and to manage the cells.

    Enhanced Printer Support for JES2:

    • Optional Setup Verification of Output Devices: An installation can disable the device start-up message issued following a device characteristics change.

    • Optional Deletion of Remote Console Messages: An installation can discard remote console messages normally routed to remote printers.

    • Forms Control Buffer Enhancement: New support allows an installation to provide a device-default forms-control buffer on local and remote printers.

    Batch Work Load Management by OPC/A:

    Operations Planning and Control/Advanced (OPC/A), the IBM product that provides automated job scheduling for MVS, has been enhanced to work with MVS/SP 3.1.3 to manage those jobs and data sets that the customer selects to use Hiperbatch. The customer specifies to OPC/A the data sets to be managed by Hiperbatch. OPC/A, knowing the production job schedule, informs the operating system when a data set in a job is to use Hiperbatch, and handles the purge when it is no longer needed. The enhancement to OPC/A Release 2 is provided through the service process as APAR PL50291.


    Operating Environment

    Machine Requirements:

    • An IBM ES/3090 Processor Model E, S, or J, at the appropriate engineering change (EC) level that supports the IBM Enterprise Systems Architecture/370, or an IBM 4381 Model Group 90E, 91E, or 92E processor. Use of Hiperbatch requires expanded storage and an ES/3090 Model 150JH, 170JH, 180J, 200J, 250JH, 280J, 300J, 380J, 400J, 500J, or 600J, or an ES/3090 Model 180S, 200S, 280S, 300S, 380S, 400S, 500S, or 600S with a no-charge engineering change (EC) 228862.

      MVS/SP Version 3 Release 1.3 continues to support I/O devices supported on previous MVS/SP Version 3 systems.

      Some devices are not allowed in an MVS B1-level active system's configuration. Refer to "MVS/ESA Planning: B1 Security" (GC28-1800) for a list of allowable devices.

    • A minimum of 8 megabytes of central storage.

    Programming Requirements:

    MVS/SP 3.1.3 requires the following products:

    • MVS Release 3.8 (5752-VS2)
    • MVS/XA Data Facility Product (DFP) Version 2.3 or Version 2.4 (5665-XA2)with a PTF or MVS/DFP Version 3.1 (5665-XA3) with PTFs
    • Assembler H Version 2 (5668-962) with a PTF for generating and maintaining the system, and using ESA architecture.
    • SMP/E Release 4 (5668-949) or higher for installation and maintenance.
    • TSO/E Version 1 Release 4 (5665-285) or TSO/E Version 2 (5665-025) for interactive support. MVS/SP 3.1 continues to provide batch support.

    The following must be installed at or above the release levels specified below to operate with MVS/SP 3.1.3:

    • RMF Version 4 Release 1.1 (5685-029) with PTF
    • EREP Version 3 Release 3 (5658-260)
    • BTAM Version 3 Release 8 base with BTAM/SP (5665-279))
    • TIOC (3.8 base)
    • GAM/SP Version 2 (5668-978)
    • ACF/TCAM Version 2 Release 4 (5735-RC3)
    • ACF/VTAM* Version 3 Release 1.1 (5665-289)
    • DFDSS Version 2 Release 3 (5665-327)
    • VM/XA SP2 (5664-308) (guest support only)
    • DATABASE 2 (DB2) Release 3 (5740-XYR)
    • CICS/VS Version 1 Release 7.0 (5740-XX1)
    • IMS/VS Version 1 Release 3 (5740-XX2)
    • ISPF Version 2 Release 3.0 (5665-319)
    • ISPF/PDF Version 2 Release 3.0 (5665-317)
    • RACF Version 1 Release 8.1 (5740-XXH)
    • Service Level Reporter (SLR) Version 3 Release 1.1 (5665-397)
    • Operations Planning & Control/Advanced (OPC/A) Version 1 Release 1.0 (5665-371, 5665-372, and 5665-373)
    • System Display and Search Facility (SDSF) (5665-488) Release 1.2.0
    • MVS/SP Version 2 MICR/OCR feature (5685-002)
    • NetView Release 2 MVS/XA (5665-362)

    To take advantage of functions provided with MVS/SP Version 3 Release 1.3, configurations with the following items installed require these or the next higher specified release level:

    • CICS/MVS Version 2 Release 1 (5665-403)
    • VM/XA SP Release 2.1 (5664-308) with PTF (guest support only)
    • IMS/VS Version 2 Release 2 (5665-332)
    • TSO/E Version 2 Release 1.1 (5685-025)
    • MVS/DFP Version 3 Release 1 with PTFs or DFP Version 3 Release 1.1 (5665-XA3)
    • A then current Release of ACF/VTAM
    • RACF Version 1 Release 9 (5740-XXH)
    • Operations Planning & Control/Advanced (OPC/A) Version 1 Release 2.0 (5665-371, 5665-372, and 5665-373)

    Virtual Storage Requirements:

    If a CICS system has a large number of VSAM files, migrating to CICS/MVS 2.1 and MVS/DFP 3.1 running under MVS/ESA can result in savings of virtual storage from the common area. The savings will be approximately 240 bytes for each VSAM string.

    Note: Virtual Storage Measurements were made in a controlled environment using standard performance workloads and methodology. The actual VSCR that any user will experience will vary depending upon considerations such as the user's program-product mix, the workload characteristics, and the system configuration.


    Compatibility

    MVS/SP 3.1.3 is upwardly compatible for most application programs. For more explicit information about interfaces that may be affected by use of MVS/SP Version 3 Release 1.3, see MVS/ESA General Information for SP Version 3 (GC28-1359).

    The JES2 component and the JES3 component with MVS/SP-JES2 Version 3 Release 1.3 and MVS/SP-JES3 Version 3 Release 1.3 run only on MVS/SP Version 3 Release 1.3 BCP. MVS/SP Version 3 Release 1.3 BCP will run with the JES2 components 1.3.6, 2.1.5, 2.2.0, and 3.1.1, and with the JES3 components 1.3.4, 2.1.5, 2.2.1, 3.1.1, and 3.1.2. This JES2 release will not co-exist in a shared spool complex (JES2 MAS) with any previous JES2 release. This JES3 release will not co-exist in a JES3 complex with any other or previous JES3 release.

    A cold start is required when installing the JES2 or JES3 component of MVS/SP-JES2 Version 3 Release 1.3 or MVS/SP-JES3 Version 3 Release 1.3. The JES2 Spool Offload Facility and JES3 Dump Job may be used to preserve the JES2 or JES3 spool contents across the required cold start.


    Performance Considerations

    Batch Processing:

    Significant reductions in MVS/ESA batch elapsed time can be realized through the systems synergy provided by the ESA/370 architecture extension available in ES/3090 Models 150JH, 170JH, 180J, 200J, 250JH, 280J, 300J, 380J, 400J, 500J, 600J, Expanded Storage, and the new Hiperbatch facility available in MVS/SP V3R1.3. The new Hiperbatch facility uses data in memory techniques to reduce I/O for those jobs which require the same QSAM or VSAM non-shared resource data sets.

    Performance tests in controlled laboratory environments and benchmarks of actual customer environments have shown elapsed time reductions of up to 60 percent depending on contention and data re-use characteristics of the individual workloads. The elapsed-time reduction depends on the amount of QSAM or VSAM non-shared resource datasets used by multiple jobs, and the amount of I/O contention within the batch workload.

    An SE AID called Hiperbatch aid (HBAID) is available through your IBM account representative. This can be used to determine whether there are datasets which might benefit from Hiperbatch processing. This aid runs in an MVS/XA or MVS/ESA environment. Also, the aid can use input describing expanded storage configuration and workload characteristics to assist in projecting the elapsed time savings potential in a specific environment.

    Use of the Hiperbatch facility requires expanded storage, one of the above listed ES/3090 models, MVS/SP V3R1.3, and a MVS/DFP V3R1 PTF or MVS/DFP V3R1.1. A customer should not need to rewrite application programs or JCL to use Hiperbatch.


    Security, Auditability, and Control

    Data security and auditability in the MVS/SP Version 3 Release 1.3 environment are enhanced by the functions available in Resource Access Control Facility (RACF) Version 1 Release 9 licensed program (5740-XXH).

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    5685-002 MVS/System Product-JES3 Version 3 Releases 1.1 and 1.2


    Abstract

    MVS/SP-JES3 3.1.1 and MVS/SP-JES3 3.1.2 are new releases of the JES3 component for the MVS/ESA environment that utilize MVS/ESA services, provide dramatic improvements in global processor performance, and remove constraints to the support of large JES3 complexes. The new JES3 components also offer enhanced function and capabilities. MVS/SP-JES3 3.1.2 offers all the function of MVS/SP-JES3 3.1.1 plus support for the Data Facility Storage Management Subsystem (DFSMS) functions of MVS/DFP V3. The BCP provided is functionally equivalent to that provided with MVS/SP-JES3 Version 3 Release 1.0.


    Highlights

    • Increased Job Number Range

    • Dramatic Reduction in Global Processor Resource Consumption

    • Dramatic Reduction in JES3 Restart Elapsed Time

    • Management of Multiple Printers in an FSS Address Space

    • Output Processing Constraint Relief

    • Enhanced Monitoring/Diagnosis

    • Continuous Systems Operation Dynamic Support for JES3 Networking

    • JES3 Spool Maintenance Facility Replaced by Enhanced Commands

    • New and Changed User Exits

    Description

    The following descriptions define the enhancements that apply to both MVS/SP-JES3 3.1.1 and MVS/SP-JES3 3.1.1. For readability, unless otherwise noted, references to MVS/SP-JES3 3.1.1 apply equally to both of the new JES3 component levels. Since MVS/SP-JES3 3.1.2 enhancements build on the MVS/SP-JES3 3.1.1 base, those descriptions are presented last.

    MVS/SP-JES3 3.1.1 represents a major effort towards removing bottlenecks and inefficient processing algorithms, thus improving the processing capacity of JES3 and its management of large complexes. By avoiding additional constraints in the future, JES3 will be able to make more effective use of the increased job number range made possible with this release. Virtual storage constraint below 16MB is not affected by this release.

    Changes in JES3 control block structure necessitate that all processors in the complex be running the same (either MVS/SP-JES3 3.1.1 or MVS/SP-JES3 3.1.2) level of the JES3 component. JES3 has been modified to enforce this requirement, thus ensuring cross-complex system integrity.

    The following describes specific enhancements to be provided.

    Expanded Job Number Range:

    With MVS/SP-JES3 2.2.1 and earlier releases, no more than 9,999 jobs could exist at the same time in a JES3 complex. This limit represents a constraint to growth, particularly for large complexes and those for whom job networking is a significant part of their workload.

    The JES3 component of MVS/SP-JES3 3.1.1 allows a job number range of up to 32,767 to be specified. Parameters defined in the initialization stream control and activate this support. In addition, the maximum number of job numbers concurrently assigned within the complex has also been extended to 32,767.

    JES3 messages that formerly displayed a JES3 job number now display a JES3 job identifier (job id). The format of the job identifier is now a three-character prefix followed by a five-digit numeric job number, right-justified (JOBnnnnn). All messages that refer to jobs now consistently use the same format: JOB jobname (job id).

    As a part of the JES3 enhancements to provide this support, the dump job (DJ) utility will now provide a facility to dump, restore, and reset jobs by job number range.

    Note: With both the above extensions, only the artificial limits imposed by earlier JES3 component levels have been changed. While many installations may be able to take advantage of the support, others may reach performance limitations as they approach the new limits.

    It is recommended that production stability be reached with MVS/SP-JES3 3.1.1 or MVS/SP-JES3 3.1.2 before enabling support of the extended job number range. Although JES3 DJ can be used to offload the JES3 jobqueue in cases of a planned back-off or reverse migration, it will not be able to reload jobs with job numbers greater than 9,999 into a system that does not support the new 32K job number range.

    Dramatic Reduction in JES3 Global Resource Consumption:

    The JES3 global's task structure and its dependency on the single- engine execution rate of the machine on which it runs has been a growth constraint for some installations. The performance objective of this release, while still retaining most of the pre-existing task structure was to reduce the resource requirement of the JES3 global and to enable the support of larger complexes.

    Three key changes contribute to a dramatic reduction in the JES3 global processor's resource consumption:

    • Changes to how JES3 schedules work to be processed on behalf of a job, the job segment scheduler (JSS) has been rewritten.

      Under the old design, JES3 used substantially larger percentages of processor utilization on the JES3 global as the number of jobs in the complex increased. The scheduling of work was also less sensitive to function priority than it should have been. While retaining the basic dispatching structure, the redesign results in better processor utilization and significantly reduces job control table (JCT) I/O processing. This reduces the rate at which JES3 global utilization increases with increased workload.

      Additional benefits of the JSS rewrite include:

      • Improved maintainability due to better segmentation of the function, and more trace information.
      • Enhanced error recovery routines and improved error handling.

    • Queueing enhancements to dispatching JES3 tasks within the JES3 address space.

      While retaining the basic dynamic support program (DSP) dispatching structure within the JES3 address space, internal enhancements to dispatching queues that allow ready-to-dispatch work to be recognized further reduce processor utilization on the global and thus allow more work to be processed.

    • Job Control Table Lookaside Data Space:

      The job control table contains the current status of jobs being processed in the JES3 complex. It is used when processing jobs, inquiring about jobs, and when modifying the information for a job. As a spool-resident data set, this is a source of considerable I/O processing for the JES3 global.

      With MVS/SP-JES3 3.1.1, JES3 now uses ESA/370* facilities and MVS/SP V3 services to keep an updated copy of the JCT data set in a data space. By using ESA/370, JES3 can reduce the amount of JCT I/O processing by as much as an additional 50 percent over the reduction provided by the JSS rewrite. JCT reads will be resolved by access to central or expanded storage, backed by paging I/O to DASD only when required. JCT I/O will be done for all writes, directly to the job control table.

      This new data space support may result in lessened sensitivity to device contention and reduce the need to completely dedicate an entire DASD volume to the JCT data set. The actual I/O reduction that an installation will experience depends on such variables as the amount of real and expanded processor storage installed on the system, the overall system paging rate, and the length of time between JCT page references.

    Measurements and analyses in a laboratory environment have shown the constraint relief in this release can provide a reduction of JES3 global processor CPU utilization of up to 34 percent, the larger savings being provided in environments with higher job throughput and larger job queues.

    Additional JES3 Performance Constraint Relief:

    Improvements were made throughout JES3 in order to optimize internal algorithms and enhance processing capabilities, including:

    • Increased Limit for USAM I/O Buffers:

      The number of USAM (user spool access method) data buffers required by a complex depends on the amount of batch work, the number of TSO users, and the number of functional subsystem (FSS) address spaces in the complex. In prior JES3 releases, the installation could specify no more than 256 pages for USAM data buffers (in the PRTPAGE parameter of the MAINPROC initialization statement).

      The limit of 256 pages for USAM buffers effectively limited the number of TSO users, FSS writers, and batch jobs that could be active. The JES3 component of MVS/SP-JES3 3.1.1 increases the limit to 16,383 or 32,767 (depending on the number of buffers residing in a page, as specified by the installation).

    • Improvements to Job Select Processing:

      Performance analyses have shown that I/O processing delays seriously constrain the selection of jobs to be processed on a JES3 main by generalized main scheduling (GMS). This release reduces the amount of I/O necessary to select jobs. In addition, processing has been reduced by shortening path lengths. As part of this change, GMS staging area trace entries (trace id 48) have been eliminated.

    This release also reduces the amount of I/O performed for each job and for all job output. These changes may also benefit user exit routines and installation-written DSPs.

    Dramatic Reduction in JES3 Restart Elapsed Time:

    User groups have identified as a key requirement improvement of the elapsed time required to restart the JES3 global. MVS/SP-JES3 3.1.1 sharply reduces the time required for a JES3 warmstart or hotstart. Enhancements include:

    • Reducing I/O activity necessary to reinitialize jobs.

    • Reducing the time required to write messages to the initialization output (JES3OUT) data set. This should result in a performance improvement during all the phases of initialization.

    • Significant changes to job validation that:

      • Detect the existence of jobs that would cause system errors and prevent outages caused by these jobs.

      • Reduce the time required to validate jobs by processing multiple jobs in parallel.

      • Isolate the failure of a job during validation to the specific job being processed.

      • Supply more diagnostic information for jobs cancelled during initialization by JES3, or by the operator, or during a restart with analysis due to invalid data or control structures.

      • Allow installations to use a new job SNAP facility during job validation to supply information about each spool control block related to the job and any errors that may be detected in the control blocks.

    Measurement and analyses of JES3 hotstarts, without the analysis option, in a laboratory environment, have shown the improvements in this release can provide a reduction of up to the times shown in the following table:

    Time to msg IAT3100 Total Jobs JES3 3.1.1 JES3 2.2.1

    1,000 37 seconds 288 seconds 5,000 81 seconds 663 seconds 9,000 142 seconds 1070 seconds 32,000 831 seconds ------------

    Time to msg IAT2645 Total Jobs JES3 3.1.1 JES3 2.2.1

    1,000 91 seconds 379 seconds 5,000 257 seconds 1019 seconds 9,000 461 seconds 1716 seconds 32,000 2576 seconds ------------

    Hotstart times were measured from the operator reply to the IAT3011 message (SPECIFY JES3 START TYPE). The first two columns give the times to the appearance of the IAT3100 message (JES3 SPx.x.x SYSTEM HOTSTART...). The second two columns give the times to the IAT2645 message (CONNECT COMPLETE) for the global.

    Management of Multiple Printers in an FSS Address Space:

    As the interactive use of MVS has increased, so has the need to provide "on-demand" output. IBM is addressing this requirement with functional subsystem managed office and departmental printers such as the 3820, 3827, and 3835 Page Printers.

    In order for JES3 to manage large numbers of these printers, and to increase the number that can be supported in a JES3 complex, the system resources required must be reduced. Thus, JES3 FSS services have been extended in MVS/SP-JES3 3.1.1 to support multiple printers, each driven by a functional subsystem application (FSA), per FSS address space. (In MVS/System Product Versions 1 and 2, JES3 FSS services only allow one printer per FSS address space.)

    This also enhancement reduces the amount of real storage associated with printer support and should allow the installation to effectively manage an increased number of printers.

    To provide more stability and usability for FSS writers, the impact of any FSA-related failure is limited to a specific device, rather than all devices managed by the FSS. The presentation of FSS-related messages is also affected by this support. Messages relating to the overall operation of the FSS address space are now routed separately from those relating to the operation of a specific FSA.

    User requirements concerned with the operation of FSS-managed devices are also being satisfied by this support:

    • The operator can now change the checkpoint interval for an FSS-managed device with a writer command.

    • The operator can change the process mode (PRMODE) of the output for a specific job with a JES3 modify command.

    • Error messages for writer commands are more descriptive, providing the operator with information about the reason for a command failure.

    • The non-process run-out interval (NPRO) specification for an FSS-managed device is now checkpointed and saved across a JES3 hotstart, making it unnecessary for an operator to re-enter the command after a hotstart.

    • The installation can now specify whether a particular print, punch or remote device is to be used as a dynamic or a hot writer using a new keyword on the DEVICE initialization statement or by a new JES3 *MODIFY command.

    • Messages are now provided with a job's output when an operator command interrupts, repositions, cancels or reschedules the output processing.

    Notes:

    1. The number of FSS applications that may be concurrently active within an address space, and thus the number of printers that may be supported, varies depending on the amount of virtual storage available below 16MB for use by the Print Services Facility/MVS (5667-275) licensed program.

    2. Some messages presented to an operator have changed because FSS-related messages are now routed separately from those relating to a specific FSA.

    3. The scope of the *FAIL,fssname command is broader now that more than one device may be active at a time in the FSS address space.

    Note: Print Services Facility/MVS Release 2.0 is required for the above functions, as well as all other advanced function printing for installations planning to use PSF/MVS with either MVS/SP-JES3 3.1.1 or MVS/SP-JES3 3.1.2.

    Output Processing Constraint Relief:

    Many installations have applications that dynamically generate, or spin off, output. With earlier JES3 releases, overall performance could be constrained as more and more spinoff data sets were queued to one job. This release improves output processing to alleviate these problems and provides better performance for end users in installations using applications such as TSO/E or office support offerings.

    The enhancements:

    • Improve performance and reduce spool I/O required when accessing or updating the JES data set summary (JDS) control block.

    • Reduce the spool I/O necessary during output service processing for jobs with an excessive number of output data sets.

    • Improve performance and reduce the I/O required to schedule output to be printed at a BSC remote work station.

    • Reduce the chances of JES3 waits or deadlocks while waiting for buffers by extending the maximum size that may be specified for the JSAM buffer pool from the old limit of 1,024 pages to 16,383 or 32,767 (depending on the number of buffers in a page, as specified by the installation).

    Laboratory measurements have demonstrated a significant improvement in the processing rate and the required I/O activity for spinoff data set processing by JES3 output service in MVS/SP-JES3 3.1.1, when compared to the MVS/SP-JES3 2.2.1 component level. These improvements should be most noticeable in installations with a very high spinoff rate per job.

    JES3 Networking (non-SNA) logical network printers and punches also process work as spinoff data sets. Thus, the rate at which these data sets are removed from the output service queue and scheduled for transmission has also been improved. These improvements are most noticeable in installations where very large amounts of job networking data is mixed with print-type spinoff data sets for a given job.

    Enhanced Monitoring/Diagnosis:

    Integration and Improvement of JES3 Monitoring Facility Functions:

    In order to protect the integrity of JES3 and to provide additional diagnostic information to JES3 users, the functions previously provided by the JES3 Monitoring Facility II (JMF II) program offering (5796-PLW) have been upgraded and have been integrated into the JES3 component of MVS/SP-JES3 3.1.1. The JMF II program offering will not be updated to support MVS/SP-JES3 3.1.1 or MVS/SP-JES3 3.1.2.

    JMF functions now also include the following enhancements:

    • The integrated JMF now writes information to the SMF data sets, thus allowing post-processing by installation-provided data reduction tools.

    • Documentation for JMF has been upgraded and is included in standard JES3 manuals.

    • JMF can now execute on a JES3 local as well as the global.

    • The maximum number of entries monitored by JMF has been significantly increased, allowing installations to examine the utilization of lower priority functions such as JSS.

    • JMF has been enhanced to improve serviceability by saving and displaying additional diagnostic information when the JMF sampling function terminates abnormally.

    • Where appropriate, JMF has been changed to support other new functions being provided by MVS/SP-JES3 3.1.1 and MVS/SP-JES3 3.1.2.

    • JMF error messages have been enhanced and converted to standard JES3 messages.

    Additional IPCS Support:

    As part of JES3's commitment for continuing IPCS (interactive problem control system) support and to improve overall serviceability, seventeen control blocks are being added to the group of JES3 control blocks users can view online using IPCS.

    Continuous Systems Operation Dynamic Support for JES3 Networking:

    To support continuous systems operations, this release allows the operator to add a node to, or delete a node from, an NJE network by issuing a command. New keywords have been added to the *F,NJE command for this purpose. With prior releases of the JES3 component, an installation was required to change the JES3 initialization stream and perform a complex-wide IPL and a warmstart in order to perform this task.

    For users of SNA networking under MVS/Bulk Data Transfer (MVS/BDT), new node definitions must still be included in the BDT initialization stream, in order for nodes dynamically added to JES3 to be functional.

    Note: It is still advisable to add or change the NJE node definitions in the JES3 initialization statements. The results of the *F,NJE command will not be checkpointed. Therefore, operators will need to reenter the commands after a hotstart or DSI in order to restore the previously introduced network status.

    JES3 Spool Maintenance Facility Replaced by Enhanced Commands:

    The functions formerly provided by the JES3 spool maintenance (JSM) facility are enhanced and are now provided using standard output service commands. Operators can use output service commands to inquire about or delete data sets. The operator can select data sets for both inquiry and modify based on their age on any output service queue (that is, WTR, BDT, or HOLD). The age specified can be modified to select by days or hours.

    Additional flexibility is provided by:

    • The ability to allow operators to delete (or otherwise modify) individual data sets from a job based on age.

    • The ability to select data sets by the time they were written to spool as opposed to the age of the job that created them.

    • The ability to request a single summary message to the console, rather than separate messages for every data set processed by inquiry and modify commands.

    Note: JSM has been deleted from JES3.

    Removal of JES3 Card-Based Utility DSPs:

    The following utility DSPs have been removed from JES3 due to their limited use:

    • Card-to-Card (CC)
    • Card-to-Printer (CP)
    • Card-to-Tape (CT)
    • Tape-to-Card (TC)

    MVS/SP-JES3 3.1.2 Support for MVS/DFP V3 DFSMS Functions:

    MVS/SP-JES3 3.1.2 offers all the functions of MVS/SP-JES3 3.1.1 plus support for the Data Facility Storage Management Subsystem (DFSMS) functions provided by MVS/DFP V3.

    JES3 has always had the capability of managing input/output resources on a complex-wide basis through its main device scheduling (MDS) functions. Since MVS/DFP V3 DFSMS support introduces a new way to define DASD resources, awareness of these resources requires full cooperation between JES3 and MVS/DFP V3; JES3 is dependent on MVS/DFP V3 for all such awareness. JES3 will continue to provide cross-complex data set integrity for requests managed by MVS/DFP V3 DFSMS support.

    MVS/DFP V3 is a prerequisite product for MVS/SP-JES3 3.1.2 installation, it is required for all installations, whether or not they choose to utilize DFSMS services.

    JES3 uses DFSMS services during C/I and MDS processing to:

    • Ensure that catalog locate processing occurs on a processor that has access to the required catalogs.

    • Ensure that jobs requiring DFSMS-managed resources execute on processors on which the resources are accessible and available.

    MVS/SP-JES3 3.1.2 also introduces the following enhancements:

    • JES3 can multitask catalog locate requests.

    • Locate processing can be performed in a JES3 C/I FSS address space.

    • JES3 provides data set integrity for new nonspecific DASD data sets which are managed by DFSMS.

    • JES3 improves data set integrity for DFHSM migrated data sets.

    Note: A PTF will be required for the "old" JES3 component to requeue jobs if the installation requires a planned back-off from the MVS/SP-JES3 3.1.2 level. Those jobs that have completed JES3 C/I processing and have not yet completed Main Service will be requeued for C/I processing on the prior JES3 level.

    New and Changed User Exits - MVS/SP-JES3 3.1.1:

    To help ensure the ability to customize and effectively use IBM software without direct source code modification, one new JES3 user exit has been added and an existing user exit has been changed. (One existing user exit has been deleted.)

    • User Exit 14 (IATUX14):

      This exit, called from initialization job validation routines, is added to allow users to perform their own validation processing of user fields in eleven key control blocks.

    • User Exit 47 (IATUX47):

      This exit, called from the JES3 Spool Maintenance facility (JSM) is deleted along with JSM and replaced by IATUX48.

    • User Exit 48 (IATUX48):

      This new exit is provided to allow the installation to override an operator command requesting that an output data set be modified or deleted based on age.

    • User Exits that reference job numbers may need to change:

      Many JES3 exits receive as input pointers to control blocks which contain a job number. Others may be dependent on, or format, EBCDIC job numbers. Since the expanded job number range provided by the MVS/SP-JES3 3.1.1 and the inclusion of the 8-character job id may affect these exits, they should be reviewed and updated where required.

      A new macro, IATXJOB, will be provided for the conversion of a job number or job id. Another macro, IATXCVB, will be provided for the conversion of an EBCDIC number to the binary format.

    • Message Processing Facility (MPF) Exit (IEAVMXIT):

      This exit allows the installation to change the destination routing or text of an MVS console message. Installations may need to modify this exit to handle the changes in the text of JES3 messages as a result of the inclusion of the job id.

    Changed User Exits - MVS/SP-JES3 3.1.2:

    • User Exit 7 (IATUX07):

      The return conventions for this exit have changed. This exit is called from Locate processing when a data set can not be found in the catalog. For data sets not managed by MVS/DFP V3 DFSMS support, the installation may now pass back the unit and volume information in a parameter list.

    • User Exits IATUX11 and IATUX61:

      The input parameters for these exits are changed.

    • User Exits IATUX46 and IATUX49:

      The invocation algorithm for these exits has been changed.


    Operating Environment

    Machine Requirements:

    MVS/SP V3 requires a 3090 Enhanced Model at the appropriate EC level that supports the IBM Enterprise Systems Architecture/370 or a 4381 Model Group 91E or 92E processor.

    Expanded storage only (ESO) Hiperspaces require expanded storage.

    Programming Requirements:

    The MVS/SP 3.1.0 BCP, at a minimum, is required for MVS/SP-JES3 3.1.1 to function.

    MVS/SP-JES3 3.1.1 requires the following as minimum levels when the products are installed:

    • Print Services Facility/MVS Release 2.0 (5667-275)
    • Report Management & Distribution System (RMDS) Release 3 (5665-310)

    In addition to the above, MVS/SP-JES3 3.1.2 requires:

    • MVS/DFP V3 (5665-XA3) (This is a prerequisite product.)

    Compatibility

    BCP/JES3 Compatibility:

    MVS/SP 3.1.0 Base Control Program will run with the JES3 components provided with MVS/SP-JES3 3.1.0, 3.1.1, 3.1.2, and with all other supported JES3 component levels, with or without the JES3 SNA NJE Enhancement installed.

    Multisystem Environment Using JES3:

    When the HJS3311 FMID (the MVS/SP-JES3 3.1.1) level, or the HJS3312 FMID (the MVS/SP-JES3 3.1.2) level, of the JES3 component is installed, it must be installed in all systems in the JES3 complex. The MVS/SP-JES3 3.1.1 and MVS/SP-JES3 3.1.2 components will not coexist in a mixed-level complex.

    For those installations that have already installed the JES3 SNA NJE Enhancement and APAR OY04734 a complex-wide Hotstart (with IPL/CLPA/MLPA) is required to move to these new levels of the JES3 component; otherwise, a Warmstart will be required due to changes in spooled control blocks.

    Coexistence in a loosely-coupled JES3 complex can only occur between processors running the same level of the JES3 component or specifically designated combinations.

    The following two sections define the service relationship of the JES3 and BCP components of the MVS/System Products. The first section defines the equivalent levels of JES3 shipped with each release of the MVS/System Product and the FMID identification of those components. The second section defines the supported BCP and JES3 component combinations.

    • FMID=HJS2329.

      The level of JES3 shipped in MVS/System Product - JES3 Version 1 Release 3.4 and 3.5, and MVS/System Product - JES3 Version 2 Release 1.2 (after December 28, 1984) and 1.3 is the same.

      Note: Although different, systems running HJS2329 and HJS2215 will be supported in a JES3 mixed-level complex until December 31, 1989, as defined in the following table.

    • FMID=HJS2215.

      The level of JES3 shipped in MVS/System Product - JES3 Version 2 Release 1.5, 1.7 and 2.0 is the same.

    • FMID=HJS2220.

      The level of JES3 shipped in MVS/System Product Version 2 Release 2.1 and MVS/System Product - JES3 Version 3 Release 1.0 is the same and may be used together in a multi-system complex.

    • FMID=HJS3311.

      The level of JES3 shipped in MVS/System Product - JES3 Version 3 Release 1.1 is new and will only work in a multi-system complex when combined with other systems running the identical JES3 level.

    • FMID=HJS3312.

      The level of JES3 shipped in MVS/System Product - JES3 Version 3 Release 1.2 is new and will only work in a multi-system complex when combined with other systems running the identical JES3 level.

    This table defines supported JES3 multi-system combinations:

    JES3 FMIDs HJS HJS HJS HJS HJS 2329 2215 2220 3311 3312 ----------------------------- HJS2329-| * | * | | | | |---------------------------| HJS2215-| * | * | | | | |---------------------------| HJS2220-| | | * | | | |---------------------------| HJS3311-| | | | * | | |---------------------------| HJS3312-| | | | | * | -----------------------------

    If the JES3 SNA NJE Enhancement (FMID JJS2353 for MVS/SP-JES3 Version 1 and FMID JJS2355 for MVS/SP-JES3 Version 2) is installed with HJS2329 or HJS2215, it must be installed on all processors in the complex.

    The following table defines the current releases of MVS/SP-JES3 and the supported JES3 FMID and BCP component combinations:

    Base Control Program Component Shipped with:

    MVS/SP Version 1 Release - |-----------| JES3 FMID |3.3|3.4|3.5| --------- |-----------| HJS2329 | * | * | * | |-----------| HJS2215 | | | | |-----------| HJS2220 | | | | |-----------| HJS3311 | | | | |-----------| HJS3312 | | | | -------------

    MVS/SP Version 2 Release - ------------------------- JES3 FMID |1.2|1.3|1.5|1.7|2.0|2.1| --------- |-----------------------| HJS2329 | * | * | * | * | * | * | |-----------------------| HJS2215 | * | * | * | * | * | * | |-----------------------| HJS2220 | | | | | * | * | |-----------------------| HJS3311 | | | | | | | |-----------------------| HJS3312 | | | | | | | -------------------------

    MVS/SP Version 3 Release - ------------- JES3 FMID |1.0|1.1|1.2| --------- |-----------| HJS2329 | *1| *1| *1| |-----------| HJS2215 | *1| *1| *1| |-----------| HJS2220 | * | * | * | |-----------| HJS3311 | * | * | * | |-----------| HJS3312 | * | * | * | -------------

    Notes:

    1. Missing columns or rows reflect components that are no longer supported.

    2. * - Designates a permissible combination.

    3. *1-To aid migration to MVS/ESA, HJS2329 and HJS2215 (with or without the SNA/NJE Enhancement), at the appropriate PTF service levels, will be supported with MVS/SP 3.1.0 and subsequent modification levels, if any, of MVS/SP Version 3 Release 1, unless otherwise stated at announcement. However, if MVS/DFP V3 is installed in the complex, the minimum supported JES3 component level will be HJS2215.

    The HJS3312 component level is required to support environments utilizing the Data Facility Storage Management Subsystem functions of MVS/DFP V3.

    Removal of JES3 Card-Based Utility DSPs:

    The following utility DSPs have been removed from JES3 due to their limited use:

    • Card-to-Card (CC)
    • Card-to-Printer (CP)
    • Card-to-Tape (CT)
    • Tape-to-Card (TC)

    Performance Considerations

    MVS/SP-JES3 3.1.1:

    The performance of the JES3 component of MVS/SP-JES3 3.1.1 is significantly improved when compared to that of MVS/SP-JES3 2.2.1 when executing equivalent functions. However, the actual performance that an installation will experience will vary depending upon such considerations as initialization options, workload, and the use of enhanced functions.

    MVS/SP-JES3 3.1.2:

    MVS-SP-JES3 3.1.2 performance is equivalent to that of MVS/SP-JES3 3.1.1 when executing equivalent functions and not activating the storage management functions of MVS/DFP V3. However, the actual performance that an installation will experience will vary depending upon such considerations as initialization options, workload, and the use of enhanced functions.

    MVS/SP-JES3 3.1.2 performance, when activating or exercising the storage management functions of MVS/DFP V3, will be provided prior to general availability.


    Security, Auditability, and Control

    Data security and auditability in the environment created by MVS/SP V3 are enhanced by the functions available in the Resource Access Control Facility (RACF) Version 1 Release 8 licensed program (5740-XXH).

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    Publications

    The following advance publications will be available as indicated.

    • GC28-1359 MVS/ESA General Information for SP Version 3 (Availability Date, April 1988)
    • GC28-1417 MVS/ESA JES3 Conversion Notebook (3.1.1) (Availability Date, September 1988)
    • GC28-1568 MVS/ESA Conversion Notebook for SP Version 3 Volume 2 (Availability Date, June 1988)

    For a current list of publications, refer to the appropriate publications option on your respective HONE system, or contact your IBM representative.


    5685-001 MVS/System Product-JES2 Version 3 Release 1.1


    Abstract

    MVS/SP-JES2 3.1.1 is a new release of the JES2 component for the MVS/ESA environment that utilizes MVS/ESA services and removes constraints to the support of large multi-access spool (MAS) complexes. The new JES2 component also offers enhanced function and capabilities for the JES2 installation. The BCP component provided with this release is functionally equivalent to that provided with MVS/SP-JES2 Version 3 Release 1.0.


    Highlights

    • Increased Job and Output Queue Limits and Job Number Range

    • Output Processing Constraint Relief

    • Expanded NJE/RJE Limits and NJE/RJE Functional Enhancements

    • Dramatically Reduced Elapsed Time for JES2 Restarts

    • Virtual Storage Constraint Relief

    • Improved Serviceability

    • Continuous Systems Operations Enhancements

    • Improved Usability

    • New and Enhanced User Exits

    Description

    MVS/SP-JES2 3.1.1 provides significant growth potential for large multi-access spool installations, NJE/RJE installations, and installations with long-running applications, as well as enhancements for all MVS/SP-JES2 V3 installations in key areas such as availability and continuous operations.

    Changes in JES2 control block structure necessitate that all processors in the complex be running the same (MVS/SP-JES2 3.1.1) level of the JES2 component.

    The following describes specific enhancements provided by this release.

    Expanded Job Number Range and Output Queue Limit:

    With MVS/SP-JES2 2.2.0 and prior releases, no more than 9,999 jobs could exist at the same time in a JES2 complex. This limit represents a constraint to growth, particularly for large complexes and those for whom job networking is a significant part of their workload.

    The JES2 component of MVS/SP-JES2 3.1.1 now allows a job number range of up to 32,767 to be specified. Parameters defined in the JES2 initialization data set control this support. In addition, the maximum number of concurrently active and queued jobs has also been extended to 32,767.

    Because more jobs running in the complex can generate more output, the maximum number of JES2 output queue entries possible in a single JES2 complex is also extended from the previous limit of 30,000 entries to 99,999 per JES2 multi-access spool complex.

    JES2 messages, commands, and SMF records that formerly displayed or used a JES2 job identifier have been changed. The format of the job identifier is now a 3-character prefix (JOB, STC, or TSU), followed by a 5-digit numeric job number, right-justified with leading zeroes.

    Expanded NJE/RJE Limits and NJE/RJE Functional Enhancements:

    As remote job entry (RJE) and network job entry (NJE) utilization has increased, so has the visibility of RJE and NJE constraints. The expanded job number range and output queue limit remove two significant constraints in job networking complexes. In addition, MVS/SP-JES2 3.1.1 provides the following enhancements for NJE/RJE installations:

    • The maximum number of NJE node definitions are increased from 1000 to 9999.

    • The maximum number of RJE definitions are increased from 4000 to 9999.

      Note: With both the above enhancements, only the artificial limits imposed by earlier JES2 component levels have been changed. While many installations may be able to take advantage of the support, others may reach performance limitations as they approach the new limits.

    • NJE node definition is now more dynamic.

      To support continuous systems operation, MVS/SP-JES2 3.1.1 allows the operator to modify the characteristics of an NJE node, including the node name of an inactive node, as defined to JES2 by issuing a $T command. Also, a new command, $ADD, may also be used to add destinations (DESTIDs) and functional subsystem (FSS) definitions.

      Note: The results of the $T and $ADD commands are not checkpointed. Thus, it is still advisable to add or change these initialization statements in the JES2 initialization data set. Otherwise, operators are required to reenter the commands after a warmstart in order to restore the previously introduced changes.

    • Usability of operator commands is enhanced.

      The operator can dynamically change, individually or in ranges, many definitions for remotes, lines, and SNA interfaces. The operator can also display these resources by range.

    Output Processing Constraint Relief for Long-Running Applications:

    Many installations have long-running online applications that dynamically generate (or spin off) output. With prior JES2 releases, spool utilization, JES2 warm start time, and job purge could become a constraint as more and more spinoff data sets were queued to one job. To alleviate these problems and to provide better capacity for end users (e.g., report distribution and office-support offerings), enhancements have been made to output processing in the MVS/SP-JES2 3.1.1 release:

    • Increased Limits for JES-Managed Data Sets:

      The defined limit on the maximum number of SYSIN and SYSOUT data sets supported during the life of a job has been extended from 32,667 (with APAR OZ93770) to 9,999,899 with the MVS/SP-JES2 3.1.1 release. This avoids constraints that could necessitate taking down a key application.

    • Reduced Amount of Spool-Residency Time for Spinoff Data Set Control Blocks:

      Each spinoff data set has an associated spool-resident control block. With the potential to spin off many thousands of these data sets during the life of a job, a great deal of spool space containing these control blocks, could remain allocated until the job purges. This release reduces the amount of residency time for these control blocks by reusing those whose data sets have already been processed, instead of waiting for job purge. Thus, potentially reducing the spool space consumed for these long-running jobs.

    • Reduced Processing for External Writers:

      This release also reduces the processing required by external writers, by only posting external writers when the selection criteria matches the output characteristics.

    Dramatically Reduced Elapsed Time for JES2 Restarts:

    Laboratory measurements have shown a reduction in the elapsed time of the job queue processing phase of an all-systems (i.e., complex-wide) warm start for MVS/SP-JES2 3.1.1 of up to 90 percent, when compared to MVS/SP-JES2 2.2.0. This percentage may vary depending on the specific customer installation. Warm start elapsed time decreases will have the most dramatic effect on those installations which have only one machine using a given SPOOL/CHECKPOINT combination. Since those systems perform an all, system warm start, the most complete warm start, each time they IPL, they will most frequently see the improvement in warm start elapsed time provided by this release.

    In prior releases, job queue processing during warm start was done by a single warm start processor. This, compounded by the large amount of I/O involved in job queue processing, lengthened the time to do a JES2 warm start for some installations. In MVS/SP-JES2 3.1.1, multiple warm start processors improve the efficiency of job queue processing during warm start.

    MVS/SP-JES2 3.1.1 also verifies the job output queues and attempts to correct any errors during warm start, without a total rebuild of the job output queues as in former releases. The new verification and error correction avoids much of the processing associated with output queues during warm start and will preserve the order of the output queues. MVS/SP-JES2 3.1.1 will rebuild the job output queues only when an non- correctable error is found.

    In addition to the warm start improvements noted above, the elapsed time for the jobqueue-processing phase for hotstarts and $ESYS restarts have been improved by as much as 85 percent, when compared to MVS/SP-JES2 2.2.0.

    Several new messages are issued during JES2 restart processing to give operators better information during the processing of the output queues. In addition, a new message informs the operator when any type of start processing has completed.

    Virtual Storage Constraint Relief (VSCR):

    With MVS/SP-JES2 3.1.1, JES2 makes use of the Enterprise Systems Architecture/370 by maintaining all internal reader protected buffers in a data space. This allows an installation to free up virtual storage from the common services area (CSA) previously used by these buffers.

    New services and macros are being provided to allow installation- written code to access the data space resident data. These services will be distributed in object code only.

    The MVS/SP-JES2 3.1.1 release provides virtual storage constraint relief for the private area of the user address space by moving the remaining scheduler work area (SWA) control blocks for SYSIN, SYSOUT, and process SYSOUT data sets into the extended user private area. This can save 16K to 112K bytes of virtual storage when compared to MVS/SP-JES2 2.2.0. The installation can still control the location of SWA by job class and for started tasks and time-sharing users.

    Subsystem interface support routines have been converted to run in 31-bit addressing mode, and most control blocks used by this support have been moved above 16MB in virtual storage. Only control blocks retaining 24-bit dependencies remain below 16MB in virtual storage. VSCR is also provided by moving the JES2 trace tables above 16MB in virtual storage into the extended common services area (ECSA). Depending on the installation's current configuration and choice of functions, the total VSCR provided for common services area by MVS/SP-JES2 3.1.1 will range from 17K to 480K bytes, when compared to MVS/SP-JES2 2.2.0.

    Improved Serviceability:

    MVS/SP-JES2 3.1.1 provides the following serviceability enhancements:

    • The $HASP185 message has been enhanced to provide additional diagnostic information after spool processing errors. The message provides additional text that indicates the affected output group and block, as well as the reason for the error.

    • Many new macros are available to allow an improved interface to services in the user environment.

    • The logging function of JES2 $TRACE facility has been modified to avoid system failures. In prior JES2 component levels, when the logger was unable to keep up with high levels of tracing activity, additional trace tables were GETMAINed from CSA. It was possible to use all of CSA, causing severe virtual storage constraint and probable system failure. Now, tracing limits can be established at initialization or with commands. When limits are reached, trace entries are discarded and the operator is notified.

    • In prior releases, it was possible in rare circumstances for an implied wait of the JES2 main task to occur as a result of the necessary serialization of JES2 tracing. This problem no longer exists.

    Continuous Systems Operations:

    The following enhancements eliminate impediments to continuous operations:

    • Directed Load of the JES2 subsystem interface support module:

      Directed load of the JES2 subsystem interface support is now possible. During JES2 initialization, if the subsystem interface support module is found in STEPLIB or LINKLST, it can be loaded into CSA key zero storage. This allows the subsystem interface support to be maintained and new releases of JES2 to be tested without an IPL/CLPA. This allows greater ease of transition (both forward and backward) from one maintenance level or release to another. Directed load is also available for installation- supplied modules.

    • Trace Enhancements:

      Along with the tracing improvements described in the previous section, improvements to the trace facility provide the ability to set or change most values related to tracing without an intervening JES2 restart.

      This release also allows the installation to define how much storage in ECSA should be allocated for trace tables. This storage will be allocated all at once and will not increase if a logging backlog occurs, although this storage definition can be changed by the operator with the $T TRACEDEF command.

    • Dynamic Definitions:

      As described in the NJE/RJE Enhancements section, NJE/RJE enhancements support more dynamic definition of NJE nodes and remote work stations. Likewise, functional subsystems (FSSs) can now be dynamically added by means of a new operator command, $ADD.

    • Improved TSO Terminal Throughput:

      If a TSO user enters a SUBMIT command while JES2 is unavailable, the terminal is freed, thus allowing the user to continue with other work.

      MVS/SP-JES2 3.1.1 also provides additional internal readers (up to a design-limit total of 32,765). This should provide additional capacity for those installations that were constrained by the number of internal readers available to process TSO submitted work.

    Improved Usability:

    Operator Command and Documentation Enhancements:

    MVS/SP-JES2 3.1.1 provides the following usability enhancements to operator commands and documentation:

    • Simplified tracing:

      The new trace facility externals are simpler and easier for operators to understand and use.

    • Automatic FSS cancellation:

      If the last functional subsystem application (FSA) under a specific functional subsystem (FSS) is drained, the FSS can be automatically cancelled based on initialization parameter definition. This eliminates the need to issue an operator command.

    • Simplified command entry:

      This release recognizes and acts on arguments that allow the specification of single targets, ranges, or generic specifications on certain initialization statements and associated commands. Particularly, this support is extended to line (LINE(nnnn) ), remotes (RMT(nnnn) ), and logons (LOGON(n) ) initialization statements, among others.

    • More complete information provided for RJE:

      Full or partial definitions can now be displayed for RMTs, LINEs, and LOGONs.

    • A number of JES2 messages are now highlighted to indicate the continuation of processing and deleted only when that processing is completed.

    • Reorganization of "MVS/ESA Operations: JES2 Commands":

      MVS/ESA Operations: JES2 Commands has been reorganized to present all commands in alphabetical order.

    New and Enhanced User Exits:

    To help ensure the ability to customize and effectively use IBM software without direct source code modification, this release provides nine new JES2 exits; eight of these exits are provided in response to input provided by the GUIDE JES2 Exits Task Force:

    • $EXIT 27 - PCE Attach/Detach.

    • Exits 28 through 35, which provide customization for JES2 subsystem interface (SSI) support.
      • $EXIT 28 - SSI Job Termination.
      • $EXIT 29 - SSI End-of-Memory.
      • $EXIT 30 - SSI Data Set Open/Restart.
      • $EXIT 31 - SSI Data Set Allocate.
      • $EXIT 32 - SSI Job Select.
      • $EXIT 33 - SSI Data Set Close.
      • $EXIT 34 - SSI Data Set Unallocate.
      • $EXIT 35 - SSI End-of-Task.

      Sample exits are provided in SYS1.SAMPLIB for all new $EXIT points.

    • This release also enhances three existing exits:

      • $EXIT 8 - Control Block I/O in User Environment. Modifications have been added to $EXIT 8 to allow an installation exit to receive control whenever a JES2 subtask or a routine running in the user address space performs any control block I/O, not just I/O for the JCT, as before.

      • $EXIT 12 - Track Allocation in User Environment. A new return code has been added to $EXIT 12 to allow an installation exit to notify JES2 that an error has been encountered during processing, and that $STRACK should exit with an error and not pass back a new track group to the caller.

    System Display and Search Facility (SDSF) Support:

    SDSF support for the JES2 component of MVS/SP-JES2 3.1.1 will be provided by a PTF for the System Display and Search Facility (SDSF) licensed program (5665-488). This PTF will be available prior to the general availability of MVS/SP-JES2 3.1.1.

    The SPOOL Display and Search Facility program offering (5798-DWX), will not support MVS/SP-JES2 3.1.1.


    Operating Environment

    Machine Requirements:

    MVS/SP V3 requires a 3090 Enhanced Model at the appropriate EC level that supports the Enterprise Systems Architecture/370 or a 4381 Model Group 91E or 92E processor. Expanded storage only (ESO) Hiperspaces require expanded storage.

    Programming Requirements:

    The MVS/SP 3.1.0 BCP, at a minimum, is required for MVS/SP-JES to function.

    MVS/SP-JES2 3.1.1 requires the following as minimum levels when the products are installed:

    • Print Services Facility/MVS Release 2 (5665-275)
    • Report Management & Distribution System (RMDS) Release 3 (5665-310)

    Compatibility

    BCP/JES2 Compatibility:

    MVS/SP 3.1.0 Base Control Program will run with the JES2 components provided with MVS/SP-JES2 3.1.0, 3.1.1, and with all other supported JES2 component levels.

    A cold start is required to migrate to the JES2 component of MVS/SP-JES2 3.1.1 release from all prior levels. The JES2 SPOOL Offload Facility may be used to preserve the contents of the JES2 SPOOL across the required cold start.

    Multisystem Environment Using JES2:

    Coexistence in a JES2 multi-access SPOOL (MAS) complex can only occur between processors using the same level of the JES2 component or specifically designated combinations.

    The following two sections define the service relationship of the JES2 and BCP components of the MVS/System Products. The first section defines the equivalent levels of JES2 shipped with each release of the MVS/System Product and the FMID identification of those components. The second section defines the supported BCP and JES2 component combinations.

    • FMID=HJE1367.

      The level of JES2 shipped in MVS/System Product Version 1 Release 3.6 is not compatible with prior levels of the JES2 component.

      Note: Although different, systems running HJE1367 and HJE2215 are supported in a mixed-level MAS complex until December 31, 1989, as defined in the following table.

    • FMID=HJE2215.

      The level of JES2 shipped in MVS/System Product Version 2 Release 1.5, and 1.7 is the same and may be used together in a MAS complex.

    • FMID=HJE2221.

      The level of JES2 shipped in MVS/System Product Version 2 Release 2.0 and MVS/System Product - JES2 Version 3 Release 1.0 is the same and may be used together in a MAS complex.

    • FMID=HJE3311.

      The level of JES2 shipped in MVS/System Product - JES2 Version 3 Release 1.1 is new and will only work in a MAS complex when combined with other systems running the identical JES2 level.

    This table defines the levels of the JES2 component that are supported when run together in multi-access SPOOL complex:

    JES2 FMIDs HJE HJE HJE HJE 1367 2215 2221 3311 --------------------------- HJE1367-| * | * | | | --------------------------- HJE2215-| * | * | | | --------------------------- HJE2221-| | | * | | --------------------------- HJE3311-| | | | * | ---------------------------

    The following table defines the current releases of MVS/SP-JES2 and the supported JES2 FMID and BCP component combinations:

    Base Control Program Component Shipped with:

    MVS/SP Version 1 Release - --------- JES2 FMID |3.5|3.6| --------- |-------| HJE1367 | * | * | |-------| HJE2215 | | | |-------| HJE2221 | | | |-------| HJE3311 | | | ---------

    MVS/SP Version 2 Release- --------------------- JES2 FMID |1.2|1.3|1.5|1.7|2.0| --------- |-------------------| HJE1367 | * | * | * | * | * | |-------------------| HJE2215 | * | * | * | * | * | |-------------------| HJE2221 | | | | * | * | |-------------------| HJE3311 | | | | | | ---------------------

    MVS/SP Version 3 Release - --------- JES2 FMID |1.0|1.1| --------- |-------| HJE1367 | *1| *1| |-------| HJE2215 | *1| *1| |-------| HJE2221 | * | * | |-------| HJE3311 | * | * | ---------

    Missing columns or rows reflect components that are no longer supported.

    * - Designates a permissible combination.

    *1-To aid migration to MVS/ESA, the HJE1367 and HJE2215 component levels will be supported with MVS/SP 3/1/0 and subsequent modification levels, if any, of MVS/SP Version 3 Release 1, unless otherwise stated at announcement. However, HJE2215 and higher JES2 component levels are required for environments utilizing the Data Facility Storage Management Subsystem functions of MVS/DFP V3.


    Performance Considerations

    The performance of the JES2 component of MVS/SP-JES2 3.1.1 is generally equivalent to that of MVS/SP-JES2 2.2.0. However, the actual performance that an installation will experience will vary depending upon such considerations as initialization options, workload, and the use of enhanced functions.


    Security, Auditability, and Control

    Data security and auditability in the environment created by MVS/SP V3 are enhanced by the functions available in the Resource Access Control Facility (RACF) Version 1 Release 8 licensed program (5740-XXH).

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    Publications

    The following advance publications will be available:

    • GC28-1359 MVS/ESA General Information for SP Version 3
    • GC28-1568 MVS/ESA Conversion Notebook for SP Version 3 Volume 2

    For a current list of publications, refer to the appropriate publications option on your respective HONE system, or contact your IBM representative.


    5685-001 MVS/System Product-JES2 Version 3 Release 1.0


    Program Number

    • 5685-001 MVS-SP-JES2 V3
    • 5685-002 MVS/SP-JES3 V3

    Abstract

    MVS/SP 3.1.0 supports the Enterprise Systems Architecture/370 (ESA/370) and provides significant new base control program (BCP) function and system services. MVS/SP 3.1.0 provides a vehicle for I/O reduction and dramatically increases virtual storage addressable by allowing access to multiple data-only spaces. It provides improved RAS by allowing programs to be isolated from data, in addition to other RAS enhancements.


    Highlights

    • Supports Enterprise Systems Architecture/370

    • Offers enhanced data handling capabilities

    • Provides increased addressability

    • Allows faster data access

    • Provides enhanced services for application development

    • Includes improved software RAS

    Description

    MVS/SP 3.1.0 expands addressing capabilities and provides enhanced data handling capabilities, faster data access, enhanced services for application development, and improved reliability, availability, and serviceability.

    MVS/ESA:

    MVS/ESA consists of MVS/SP V3 and MVS/DFP V3. MVS/ESA is the primary delivery vehicle for future MVS and DFP functional enhancements and constraint relief.

    IBM intends to enhance major IBM subsystems (CICS/MVS*, DB2*, IMS, TSO/E, JES2, JES3) using the facilities provided by MVS/ESA.

    Support for Enterprise Systems Architecture/370:

    MVS/SP 3.1.0 uses ESA/370 and provides a base for IBM subsystems and user applications to take advantage of the architectural extensions.

    • Provides increased addressability by allowing the creation and access of data spaces.
    • Provides faster access to data by reducing the number of I/O operations to DASD through new system services use of data spaces. User applications can also use these system services to enhance performance.
    • Simplifies installation management through use of new system services.

    While offering significantly extended addressability through access to multiple address spaces and data spaces, MVS/SP 3.1.0 is compatible with existing 24-bit and 31-bit subsystems and user applications.

    Data Spaces:

    MVS/SP 3.1.0 allows the creation of data-only spaces called data spaces. Each data space can provide up to two gigabytes of virtual storage for data. While an address space contains system programs and data plus user programs and data, a data space contains only data (or programs stored as data). Therefore, within a data space, all addresses are available to the application. Because access to a data space is controlled by the hardware, data spaces enhance data isolation.

    Assembler application programs can use data spaces directly, and data- in-virtual processing is extended to allow users to map data-in-virtual objects into a data space, as well as into an address space. Subsystems and user applications can have simultaneous access to multiple address spaces, multiple data spaces, or both. Shared data spaces permit efficient and controlled sharing of data among multiple address spaces.

    Appropriate controls for data spaces are provided for installation management.

    New system functions take advantage of data spaces, so users will see immediate benefit; user-written Assembler language programs can use data spaces directly; and applications can use new system services to take advantage of a specific type of data space, called a hiperspace.

    Hiperspaces:

    A high performance space, or hiperspace, is designed to provide high- performance storage and retrieval of data. A hiperspace never resides in central storage. Special new services are used to transfer data between an address space and a hiperspace. This data is accessed and transferred in 4K blocks on 4K boundaries. Two kinds of hiperspaces can be defined, standard and expanded storage only (ESO).

    A standard hiperspace resides in expanded storage or, when expanded storage is not available, on auxiliary storage. Assembler language programs can use new real storage manager (RSM) services to access standard hiperspaces and programs written in high-level languages can use new data window services to access standard hiperspaces.

    Expanded storage only hiperspaces are for use by authorized programs and can only be used on processors that have expanded storage. An expanded storage hiperspace can be viewed as a high-speed storage device for temporary data or as a processor buffer for permanent data. While a data space can reside in processor storage or on auxiliary storage and is subject to normal storage contention and paging activity, an expanded storage only hiperspace resides only in expanded storage and never resides in central storage or on auxiliary storage (available December 1988).

    System Services:

    Data Window Services:

    Data window services are a set of system services accessible by calls from high level languages. Access to permanent data-in-virtual objects is possible, as well as access to temporary objects. Using data window services, high-level language applications can define large temporary and permanent collections of data that the application can access. This data can be seen and manipulated through virtual storage windows in an application program address space. A window is a user-defined area that maps portions of the data.

    A temporary object lasts for the life of the creating task and can span multiple hiperspaces. Data window services make these objects appear as a single seamless entity. A permanent object resides in a VSAM linear data set, which can contain up to 4 gigabytes of user data.

    Data window services support calls from FORTRAN, PL/I, COBOL, and Pascal, as well as from Assembler language programs. Applications can call these services in 24-bit and 31-bit addressing mode. Standard high- level language or Assembler statements are used to manipulate data in the window (available December 1988).

    Note: The currently available IBM C for System/370 Program Offering (5713-AAH) is not supported on MVS/SP V3 as previously announced.

    Virtual Lookaside Facility (VLF):

    VLF provides a set of services that allow authorized programs to store named data objects in data spaces managed by VLF and to retrieve these objects by name on behalf of users in multiple address spaces. The primary use of VLF is to provide a high-performance means of retrieving frequently used named objects from virtual storage as an alternative to repeated DASD retrieval.

    VLF is a documented interface and can be used by other facilities. An application that uses VLF can sometimes obtain additional performance improvement by processing the DASD objects and placing them in VLF in a ready-to-use format. TSO/E V2, for example, uses VLF for "pre-compiled" CLISTs, and Library Lookaside, described below, also uses VLF.

    For VLF objects that correspond to members of partitioned data sets, VLF automatically purges the objects from VLF storage, within a single system, if they are updated on DASD.

    Library Lookaside (LLA):

    In MVS/SP 3.1.0 LNKLST lookaside is extended to manage specified libraries outside the LNKLST and is renamed Library Lookaside (LLA). LLA maintains and controls in-storage copies of library directories. This eliminates directory search I/O for the data sets LLA is managing. Installations can dynamically add and remove libraries from LLA's management and can selectively refresh members and libraries managed by LLA. In addition, LLA dynamically identifies the most active load modules in the data sets it is managing and places them in a VLF data space for subsequent retrieval. This reduces the I/O load resulting from repeatedly fetching active modules from DASD.

    The advantages of Library Lookaside include:

    • Reducing the need for system tuning by reducing the I/O activity for LLA-managed libraries.
    • Simplifying library maintenance by shielding the system from incomplete library updates and permitting selective LLA updates.
    • Increasing growth capacity for LLA-managed libraries by preventing I/O rates from growing to the point where contention would result.
    • Increasing system availability by reducing the number of IPLs required for library changes.

    Support for non-LNKLST libraries and the ability to dynamically add and remove LLA-managed libraries will be available December 1988.

    Disabled Reference (DREF) Storage:

    Programs that run disabled on systems that include expanded storage can take advantage of new virtual storage subpools that provide access to disabled reference (DREF) storage. When stolen, pages in these subpools move only to expanded storage and thus can be retrieved synchronously without I/O from a page data set. Thus, disabled programs that use DREF storage do not have to fix pages, which can reduce long-term use of real storage.

    RAS:

    MVS/SP 3.1.0 provides substantial RAS benefits, including more than 75 functional RAS enhancements that satisfy more than 25 customer RAS requirements. The following are among the more significant improvements:

    • Automated spin loop recovery provides recovery from excessive spin loop time-out conditions without operator intervention by initiating a series of pre-defined recovery actions.

    • Stand-Alone Dump is enhanced to block output records written to the dump tape. This enhancement increases dump data tape capacity and may reduce the elapsed time required to take a Stand-Alone Dump.

    • The duration of system non-dispatchability caused by SVC dump is substantially reduced, thus improving system availability.

    • IPCS provides enhanced dump formatting and analysis, dialog improvements, and additional customization options. IPCS provides comprehensive support of the new architecture by automatic translation of the new addressing mechanism. IPCS provides a functional replacement for PRDMP. Print dump (PRDMP) services are no longer available with MVS/SP V3.

    • A new component trace facility allows the operator to dynamically activate individual component traces and to select and modify trace options. RSM, VLF, and LLA make use of this trace facility.

    • The operator can remove a local page or swap data set from use dynamically. This allows the operator to re-configure the paging environment without a re-IPL.

    • The operator can display or dynamically modify missing interrupt handler (MIH) time intervals without a re-IPL.

    • RSM provides new diagnostic features that can be used in debugging, including a new trace exit and an IPCS RSMDATA subcommand to replace an RSM PRDMP exit.

    Resource Management Improvements:

    • The maximum number of slots on page data sets and swap data sets has increased, thus enabling an installation to increase its available paging capacity.

    • Expanded storage is used to relieve the constraint on real storage below 16MB. This enhancement will have particular benefit for large TSO/E environments (available December 1988).

    • Virtual I/O (VIO) support of temporary data sets is enhanced to exploit expanded storage, resulting in improved application performance, improved response time for interactive applications, and improved batch processing time.

    • Checkpoint/restart can now operate with the scheduler work area (SWA) above 16MB.

    Usability Improvements:

    • Data in virtual is enhanced to provide improved performance for sequential use of linear data sets.

    • Changes in the volume attribute list make it easier to maintain, allow specification of a default USE attribute for volumes, and reduce the need for user modification to MVS code.

    • JES2 users can now use new macros and TSO/E commands to specify output print characteristics dynamically.

    • TSO/E SMF records now include the terminal identifier.

    Global Resource Serialization Improvements:

    Global resource serialization includes enhancements that improve performance and capacity. Changes in ring processing increase the speed with which global resource serialization can grant access to an available global resource and improve the response time for dequeue requests. The amount of data needed to process requests for global resources is reduced and the space available for handling these requests is increased. These changes increase the rate of requests for global resources that global resource serialization can handle and improve the speed with which it can process these requests (available December 1988).


    Operating Environment

    Machine Requirements:

    MVS/SP V3 requires a 3090 Enhanced Model at the appropriate EC level that supports the Enterprise Systems Architecture/370 or a 4381 Model Group 91E or 92E processor. Expanded storage only (ESO) hiperspaces require expanded storage.

    Programming Requirements:

    MVS/SP 3.1.0 requires the following products:

    • MVS Release 3.8 (5752-VS2)
    • MVS/XA Data Facility Product (DFP) Version 2.3 (5665-XA2) with a PTF or MVS/DFP Version 3.1 (5665-XA3)
    • Assembler H Version 2 (5668-962) with a PTF for system generation, maintenance, and use of the new architecture in MVS/SP V3
    • SMP/E Release 4 (5668-949) for installation and maintenance
    • Interactive System Productivity Facility (ISPF) Version 2 Release 3.0 (5665-319) for use of the IPCS dialog programs
    • TSO/E Version 1 Release 4 (5665-285) or TSO/E Version 2 (5685-025) for interactive support. MVS/SP 3.1 continues to provide TSO batch support.

    Users of the following products must install the specified release levels in order to operate with MVS/SP V3:

    • RMF Version 4 Release 1 (5685-029)
    • EREP 3.3 (5658-260)
    • BTAM (3.8 base with BTAM/SP (5665-279))
    • TIOC (3.8 base)
    • GAM/SP 2.0 (5668-978)
    • ACF/TCAM Version 2 Release 4 (5735-RC3)
    • DFDSS 2.3 (5665-327)
    • VM/XA SP 2 (5664-308) (guest support only)
    • IBM Database 2 (DB2) Release 3 (5740-XYR)
    • CICS/VS Version 1 Release 6.1 (5740-XX1)
    • IMS/VS Version 1 Release 3 (5740-XX2)
    • ISPF 2.3.0 (5665-319)
    • ISPF/PDF 2.3.0 (5665-317)
    • RACF 1.8 (5740-XXH)
    • Service Level Reporter (SLR) Version 3 Release 1.1 (5665-397)
    • Operations Planning & Control/Advanced (OPC/A) Version 1 Release 1.0 (5665-371, 5665-372, and 5665-373)
    • System Display and Search Facility (SDSF) (5665-488) Release 1
    • MICR/OCR Feature of MVS/SP V3.

    Configurations with the following products installed require the specified release levels in order to take advantage of functions provided in MVS/SP 3.1.0:

    • CICS/MVS Version 2 Release 1 (5665-403)
    • IMS/VS Version 2 Release 2 (5665-332)
    • TSO/E Version 2 (5685-025)
    • MVS/DFP Version 3.1 (5685-XA3)

    Virtual Storage Requirements:

    MVS/SP 3.1.0 requires an additional 30K to 45K of common area virtual storage below 16MB virtual.


    Compatibility

    BCP/JES2 Compatibility:

    The JES2 component shipped with MVS/SP-JES2 3.1.0 is unchanged from that shipped with MVS/SP-JES2 2.2.0. The requirements for its installation were defined in the announcement of that product.

    In addition to the JES2 component shipped with this release, the installation has the option of running the MVS/SP 3.1.0 Base Control Program with the JES2 component provided with MVS/SP-JES2 1.3.6, or with that provided with MVS/SP-JES2 2.1.5 or 2.1.7.

    A cold start is required to migrate to the JES2 component MVS/SP-JES2 3.1.0 release. The JES2 Spool Offload Facility may be used to preserve the contents of the JES2 spool across the required cold start.

    When the HJE2221 FMID (the MVS/SP-JES2 2.2.0) level of the JES2 component is installed, it must be installed in all systems in the JES2 complex.

    BCP/JES3 Compatibility:

    The JES3 component shipped with the MVS/SP-JES3 3.1.0 is unchanged from that shipped with MVS/SP-JES3 2.2.1. The requirements for its installation were defined in the announcement of that product.

    In addition to the JES3 component shipped with this release, the installation has the option of running the MVS/SP 3.1.0 Base Control Program with the JES3 component provided with MVS/SP-JES3 1.3.4 and 1.3.5, or with that provided with MVS/SP-JES3 2.1.2 (shipped after December 28, 1984), 2.1.3, 2.1.5, or 2.1.7 (with or without the JES3 SNA NJE Enhancement installed).

    For those installations that have already installed the JES3 SNA NJE Enhancement and APAR OY04734 a complex-wide hotstart (with IPL/CLPA/MLPA) is required to move to the HJS2220 level of the JES3 component; otherwise, a warmstart will be required due to changes in spooled control blocks.

    When the HJS2220 FMID (the MVS/SP-JES3 2.2.1) level of the JES3 component is installed, it must be installed in all systems in the JES3 complex.


    Security, Auditability, and Control

    Data security and auditability in the environment created by MVS/SP V3 are enhanced by the functions available in the Resource Access Control Facility (RACF) Version 1 Release 8 licensed program (5740-XXH).

    User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.


    Publications

    The following advance publications will be available as indicated. To order, contact your IBM marketing representative.

    • GC28-1359 MVS/ESA General Information for SP Version 3
    • GC28-1568 MVS/ESA Conversion Notebook for SP Version 3 Volume 2

    Trademarks

    (R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

    ** Company, product, or service name may be a trademark or service mark of others.