You are on page 1of 8

Future of MVS at the University of Alberta Campus CAUSE INFORMATION RESOURCES LIBRARY The attached document is provided through

the CAUSE Information Resources Library. As part of the CAUSE Information Resources Program, the Library provides CAUSE members access to a collection of information related to the development, use, management, and evaluation of information resources- technology, services, and information- in higher education. Most of the documents have not been formally published and thus are not in general distribution. Statements of fact or opinion in the attached document are made on the responsibility of the author(s) alone and do not imply an opinion on the part of the CAUSE Board of Directors, officers, staff, or membership. This document was contributed by the named organization to the CAUSE Information Resources Library. It is the intellectual property of the author(s). Permission to copy or disseminate all or part of this material is granted provided that the copies are not made or distributed for commercial advantage, that the title and organization that submitted the document appear, and that notice is given that this document was obtained from the CAUSE Information Resources Library. To copy or disseminate otherwise, or to republish in any form, requires written permission from the contributing organization. For further information: CAUSE, 4840 Pearl East Circle, Suite 302E, Boulder, CO 80301; 303449-4430; e-mail To order a hard copy of this document contact CAUSE or send e-mail to

University of Alberta Computing & Network Services Technology Plan

Future of MVS at the University of Alberta Campus ,

Computing and Network Services (CNS) Room 103 General Services Bldg. Telephone 492-9327

Abstract: This is one within a series of documents detailing the various components of a Technology Plan. Over the past twenty years the University has invested heavily in System/370 architecture computers for administrative applications. Now, however, a new paradigm of computing exists, client/server technology allowing dramatic improvements in the functionality of computing applications. This document explores the issues surrounding the move of system services from MVS based to a client/server based computing. The content will be under review as work continues, leading to a composite Technology Plan scheduled for completion in June 1993. MVS Environment Currently the central computer used for administrative applications is an Amdahl 5880 running the MVS/XA operating system. Most, if not all, computing on this machine supports the administrative processes of the University. The focus of this paper discusses the system service software that exists to support the administrative applications in the MVS/XA operating environment. A suite of software products supports this environment. MVS Software DSF, EREP, DFP, BTAM, DSS, HSM, TLMS ACF2 DCF, DLF Resolve, CMF, IMF, Astex, MICS, PMO, QFETCH Telecommunications SSP, NCP, VTAM, H015, ACCESS, TPX, IMS/DC, CICS Printing JES328X, XADI Languages Assembler, COBOL, PL/I, GIS/VS, SAS, ADF Databases IMS/DB Applications DOBIS, Interpers Tools TSO, ISPF, IIPS, BTS, SMP/E, INFO, Syncsort, Roscoe, Librarian, EasyPROCLIB, ESP Operating System MVS/XA, JES2 Data Management Security Word Processing Performance

This environment is used to support administrative applications including: Library Catalog, Student Records, Financial, Human Resources, Payroll, Alumni, Extension and Physical Plant. Most applications have been written in COBOL and ADF using IMS databases. Queries against IMS data are written in GIS/VS, a language that was functionally stabilized by IBM ten years ago. Some applications have been purchased and implemented with significant local modifications: DOBIS, the Library Catalog; Interpers, Personnel Management; SIGL, General Ledger; and STAR, Student Advising System. The University has recently decided to embrace the client/server technology. The Library has decided to migrate the library catalog from MVS to a turnkey DEC computer running the VMS operating system. Many other departments have proceeded with the migration of MVS based applications to client/server environments using a variety of hardware and software platforms. CNS in consultation with client departments has chosen to focus on using the Oracle RDBMs and tools across the campus. Clearly, the era of MVS based mainframe computing is coming to an end. The anticipated demise of MVS is by the end of the decade. (Reference the Future of the System/370 Architecture on the University of Alberta Campus). Information Systems Today Centralized MVS Based Proprietary Software and Hardware Hard to Use Inflexible Information Systems Tomorrow Distributed Interoperable; scaleable

Easy to Use Flexible; easier to change; adaptable to organizational and regulatory changes High Application Maintenance Significant time and cost savings in application maintenance Obsolete Programming Tools Relational technology; 4 GL languages; CASE tools Centrally Managed Departmentally Managed Applications Applications Tactical Issues There are no computer tools that will magically take existing applications and implement them in a client/server environment. There are not limitless funds which will enable the growth of the client/server environment without the parallel downsizing of the MVS environment. There are no easy solutions to the turmoil and uncertainty that University personnel will face. The University is in the midst of profound change, which if managed wisely will enable tremendous opportunities. The challenge is then to migrate information systems from a MVS mainframe based computing platform while maintaining a functional, stable environment for legacy applications. The University is caught between rapidly changing technology and demands to maintain and indeed to enhance current

information systems. Using techniques developed a generation ago, the University has been unable to develop systems fast enough leading to an applications backlog and costly maintenance overhead. To meet the dual challenge of improving productivity and enhancing quality at this time, CNS sees it's role as one of guidance and leadership. * CNS in providing guidance to the campus, must have a goal of enabling a seamless, integrated set of information systems. CNS must be willing to make difficult decisions regarding the quantity of maintenance that will be allowed on the existing legacy applications and the MVS software base. CNS must provide leadership in determining the order in which information systems will be re-engineered into the new client/server environment. CNS must be cognizant that the effort required to reach these goals is substantial and be proactive in using information already gathered from the Business Systems Modeling Process to minimize this effort. CNS must support and encourage system development throughout the University. CNS must be willing to search for industry solutions to information systems needs and be willing to share solutions with other educational institutions. CNS must be aware of the significant opportunity and challenge being presented to campus and be committed to and participating in potential subcommittees and Task Forces. CNS must be aware of the challenge presented to personnel and be committed to their continued education and training. CNS must consider purchasing information systems where appropriate. CNS must ensure that access to IMS legacy data is available from the Oracle tools.

* *

* *

Technical Issues The move to client/server technology from MVS mainframe based technology will require that solutions to several technical issues be resolved. CNS is already exploring solutions to many of these issues, others will need addressing in the near future. * Authentication in a networked environment is a method by which the identity of users is authorized prior to access to a resource or data being granted. Kerberos from MIT's Project Athena is becoming the industry standard with it's acceptance by the Open Software

Foundation (OSF) as an integral part of their Distributed Computing Environment. CNS is currently evaluating whether "Kerberizing" the University network is possible. * System administration in a distributed environment can be very labor intensive and achieving commonalty can become a nightmare. Geographically diverse, heterogeneous machines with multiple copies of software must be administered so that the complexities are transparent. OSF, the Open Software Foundation, has adopted a standard suite of integrated system management tools which will simplify the management of such an environment. The suite is called the Distributed Management Environment or DME. CNS will install and support DME when it becomes commercially available. Database backups will require that point-in-time application recoveries are possible. CNS will provide such backup functionality for the Enterprise Servers and major Departmental Servers. Performance management and capacity planning of distributed databases across heterogeneous machines will be necessary. Printing should be distributed in nature, that is, it should be technically possible to print from any workstation to any printer on the network. Many departments run jobs according to schedules. CNS will need to acquire software to handle job scheduling and submission. Source code management needs to be considered. The distributed environment must be capable of controlling and archiving changes to source code. Document Management and the electronic transmission of forms across the campus is emerging as a viable technology. Financial Issues

The move to client/server technology for Information Systems will result in two platforms being supported during the migration. Clearly, we must reduce and rationalize expenditures on MVS based technologies to ensure that finances are available for the new platforms. The challenge is to continue to offer a stable, functional environment for the MVS based information systems until their migration is complete while at the same time reducing costs. The Library System, DOBIS, currently uses approximately 30% of MVS's resources. The move of Library Systems to another platform along with the decline of MTS usage will allow the consolidation of the MTS and MVS systems on one mainframe resulting in a reduction in hardware expenditures. This will happen sometime during the 93/94 fiscal year. Managing the Migration

The demise of MVS must be managed in such a way that the migration is orderly and the campus is kept informed so that manpower and financial resources are used wisely. CNS proposes that a group of CNS staff from throughout the department be responsible for planning and executing the migration. This group will report semi-annually to the Information Systems Advisory Committee. Proposed Time-table for the Demise of MVS Software The more difficult decision is how to reduce MVS software expenditures. The software on MVS must be rationalized and those functions that are either better handled on the workstation, such as word processing, or those functions that are not used heavily, such as ESP (job submission), or those functions that we can do without, such as INFO should be removed from the MVS mainframe. Work has begun on rationalizing the MVS software. The following tables shows how some of the software can be phased out over the next six years. 93 94 95 96 97 98 Rationalization /9 /9 /9 /9 /9 /9 4 5 6 7 8 9 D . . . . . Used by DOBIS. Not needed after DOBIS gone. D . . . . . DOBIS will not be needed after the Library moves their catalog to another platform. D . . . . . Job Submission Package, not fully implemented. D . . . . . CBT (computer based training) for GIS/VS, no longer needed. D . . . . . Monitor for IMS. Will continue to run but will no longer be upgraded. D . . . . . On-line source of MVS and IBM software information for technical support. Will use other means to access information. D . . . . . Monitor for CICS. Not needed after CICS gone. D . . . . . SAS graphing package. Will use other systems when graphing is required. * D . . . . MVS based word processing. Better done on workstations (more powerful packages). * D . . . . Personnel Management system should be rewritten by this time. * D . . . . Used to print DCF documents. Will not be required after DCF gone. * * D . . . GIS/VS queries should be converted to ORACLE by this



MICS * Accounti ng JES328X *

* *

D *

. D

. . . .


* *

* *

* *


. . . .


. .

time. Accounting package may be removed if CNS stops charging for MVS based services. Allows printing from MVS to remote printers. A distributed print service should be available by this time. Hyperchannel. All departments should be on the campus backbone by this time. Telecommunications software which allows connections to MVS. Used by VOCOMM and others. Should be redundant by this time. Used for time sharing users. Much of this type of work will be happening on workstations by this time. However, TSO ids will be granted for those persons still requiring time sharing access to MVS.

D indicates when the demise of a software package will occur * indicates the software package is available on MVS . indicates the software package is no longer available. 93 94 95 96 97 98 Rationalization /9 /9 /9 /9 /9 /9 4 5 6 7 8 9 Astex * * * * D . DASD monitor. Used for performance and tuning. Expected workload on MVS will be low enough to discontinue monitoring. Harbor * * * * D . An alternative platform will be found for Networked Workstation Backup facilities. Libraria * * * * D . Source code management will be n handled in a distributed manner by this time. MICS * * * * D . Used for MVS performance Performa tuning. Expected workload on nce MVS will be low enough to stop tuning MVS. Access * * * * * * Used for TCP/IP access to MVS. ACF2 * * * * * * Used for MVS security. ADF * * * * * * Used for on-line screen generation. Assemble * * * * * * Language that MVS software r written in. BTS * * * * * * Terminal emulator used to test ADF code. CMF * * * * * * MVS usage records. COBOL * * * * * * Language that Information


* *

* * * * * * * * * * *

* * * * * * * * * * * * * * *

* * * * * * * * * * * * * * *

* * * * * * * * * * * * * * *

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Syncsort * TPX * TSO/ISPF * VTAM *

Systems written in. IBM products that are used for data backups, DASD definitions, storage management, etc. JCL procedures for Information Systems. IMS database. IMS telecommunications. Job entry system, used for SPOOL, job submission. Reads and processes system usage records. Operating system. IMS performance enhancer. Can be removed when key IMS systems are migrated. Used for technical support. IMS performance enhancer. Statistics product used for reading MVS records. Used for MVS system maintenance. Sort package. Front-end software for using MVS. Time-sharing and editing. Terminal definitions and access.

D indicates when the demise of a software package will occur * indicates the software package is available on MVS . indicates the software package is no longer available.