WO2004031890A9 - System and method for expediting and automating mainframe computer setup - Google Patents
System and method for expediting and automating mainframe computer setupInfo
- Publication number
- WO2004031890A9 WO2004031890A9 PCT/US2003/027935 US0327935W WO2004031890A9 WO 2004031890 A9 WO2004031890 A9 WO 2004031890A9 US 0327935 W US0327935 W US 0327935W WO 2004031890 A9 WO2004031890 A9 WO 2004031890A9
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mainframe computer
- operating system
- computer system
- mainframe
- module
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Definitions
- This invention is directed to installing an operating system on an information processor, and more particularly to using a personal computer to perform a remote and automated upgrade of a mainframe computer operating system.
- MQ INTEGRATOR supporting CICS integration with extended systems
- MQ SERIES EVERYPLACE supporting personal digital assistant, "PDA,” applications
- MQ EVENT BROKER providing telemetry integration
- MQ WORKFLOW providing support for AIX, HP-VX, Solaris, and WINDOWS NT/WINDOWS 2000
- mainframe computer systems remain a viable and cost-effective data management tool for many organizations.
- mainframe computer system While access to data on mainframe computer systems has become significantly more flexible, the installation and maintenance of mainframe computer system operating systems remains an arduous task. Installing and configuring a mainframe computer system depends, in large part, on the operator's technical skill level. For example, in order to set up or upgrade a mainframe computer system, referred to herein, generally, as an initial program load ("IPL"), a skilled mainframe computer systems programmer is required. Unlike personal computers that automatically "boot-up" after receiving power (i.e., being turned on), a mainframe IPL is considerably complex and time-consuming. For example, one or more skilled technicians typically expend three to four days to upgrade a mainframe computer operating system and prepare the system for an LPL.
- IPL initial program load
- FIG. 1 a prior art arrangement for upgrading an operating system of a mainframe computer.
- a mainframe computer system 2 communicates with a client system 4.
- Client computer system 4 can be any device capable of emulating a terminal of mainframe computer system 2.
- client computer system 4 can be a personal computer running 3270 terminal emulation software.
- client computer system 4 can be a "dumb" terminal that operates solely as a terminal of mainframe computer system 2.
- a user of client computer system 4 is a skilled mainframe computer systems programmer who is capable of performing complex upgrades to the mainframe computer operating system and environment.
- mainframe computer system programmers and/or managers continues to rise as younger systems programmers remain attracted to small-scale computing platforms, such as personal computers and mini computers.
- the average age of skilled mainframe system programmers, capable of installing, configuring and maintaining mainframe computer systems rises with each passing year.
- mainframe computer system programmers find it increasingly difficult to efficiently install new technologies, for example, the family of WEBSPHERE MQ products, and mainframe storage and security based systems (e.g., TIVIOLI).
- TIVIOLI mainframe storage and security based systems
- the present invention is directed to solving the above-identified problems associated with mainframe computer system set-up and maintenance, specifically for operating systems.
- the present invention provides a system for upgrading an operating system on a mainframe computer system, including generating a base operating system that comprises a series of mainframe computer operating system components, and transferring the base operating system to a mainframe computer system.
- the present invention performs "discovery" on the mainframe computer system in order to receive profile information of the configuration of the mainframe computer system.
- the profile information is directed to hardware and software components existing on the mainframe computer system prior to an operating system upgrade, and is used by the present invention to ensure a similar environment exists after the upgrade to the mainframe computer operating system is performed.
- the mainframe computer system After the base operating system is installed on the mainframe computer system 2, and the environment of the mainframe computer system is configured to represent the mainframe computer system prior to the upgrade process, the mainframe computer system has an IPL performed thereon. After the mainframe computer system is IPL'd, then the mainframe computer system is customized to provide for, for example, external hardware devices (e.g., network adapters, tape drives and back up systems), remote communications (e.g., DNS and TCP/IP settings), and to configure partitioned data sets and corresponding members.
- external hardware devices e.g., network adapters, tape drives and back up systems
- remote communications e.g., DNS and TCP/IP settings
- Figure 1 is a block diagram illustrating devices used for a prior art mainframe computer operating system upgrade
- Figure 2 is a block diagram illustrating the devices associated with a mainframe computer operating system upgrade in accordance with the present invention
- Figure 3 is a flowchart illustrating the steps associated with so-called “discovery” processes in accordance with the present invention
- Figure 4A is a flowchart illustrating the steps associated with installing a base operating system on a mainframe computer system in accordance with the present invention
- Figure 4B is a flowchart illustrating the continued steps associated with installing a base operating system on a mainframe computer system in accordance with the present invention
- Figure 4C is a flowchart illustrating the continued steps associated with installing a base operating system on a mainframe computer system in accordance with the present invention
- Figure 4D is a flowchart illustrating the final steps associated with installing a base operating system on a mainframe computer system in accordance with the present invention
- Figure 5 A is a flowchart illustrating the steps associated with customizing an upgraded operating system for a mainframe computer system in accordance with the present invention
- Figure 5B is a flowchart illustrating the continued steps associated with customizing an upgraded operating system for a mainframe computer system in accordance with the present invention.
- Figure 5C is a flowchart illustrating the final steps associated with customizing an upgraded operating system for a mainframe computer system in accordance with the present invention.
- the present invention simplifies the requirement for user intervention, and dramatically shortens the time typically required to upgrade, configure and maintain an operating system for a mainframe computer system 2.
- the present invention employs a plurality of computer hardware and software systems that preferably automatically gather information from an existing mainframe computer system, and use the information for upgrading and maintaining the same or another system.
- the term, "upgrade” refers, generally, to installing a mainframe computer operating system, and using, in part, environment settings and other configuration settings from an existing system therefor.
- the mainframe computer system receiving the upgrade may or may not be the same computer system that provides the environment and configuration settings used for the upgrade.
- the present invention is concerned with mainframe computer systems. More particularly, the present invention is directed to providing an automated system and method for automating and simplifying the many complex steps associated with upgrading an operating system on a mainframe computer system.
- the present invention can be used to install extremely complex mainframe software applications, for example, WEBSPHERE MQ products.
- WEBSPHERE MQ products references to WEBSPHERE MQ products, T-NOLI, DB2 and other mainframe software applications and/or products are directed to the secondary concern of the present invention, over the primary concern of upgrading an operating system on a mainframe computer system. Such references are not intended to represent a primary purpose or primary concern of the present invention in any way.
- the present invention preferably automates the mainframe computer operating system upgrade process by automatically employing a series of directives typically required of a skilled mainframe computer systems programmer.
- a mainframe computer system 2 By preparing a mainframe computer system 2 to automatically perform an IPL, and, thereafter, automating a series of processes to configure the operating system, and further to install optional products, the present invention decreases the amount of time required, and also lowers the required operator skill-level for prior art mainframe computer system operating system upgrades.
- Figure 2 shows an example arrangement for upgrading mainframe computer operating systems in accordance with the present invention, and designated generally as mainframe upgrade system 10.
- a mainframe computer system 2 interfaces with a client computer system 4 via a CD-ROM drive 6 and communication network 8.
- the client computer system 4 includes storage for data, for example, a database 12, and uses the data stored therein to provide information directed to the mainframe computer system 2 for the operating system upgrade, installation and maintenance.
- Mainframe computer system 2 and client computer system 4 are typical devices suitable for performing the functions required of host and client systems, respectively.
- each client computer system 4 is a personal computer device capable of accessing a global computer network 8, such as the Internet.
- Mainframe computer system 2 is a mainframe computer system, for example, an IBM System 90.
- each mainframe computer system 2 and client computer system 4 can be logically and physically located anywhere in the world.
- the control programs running on mainframe computer system 2 and on client computer system 4 can be written in any language suitable for programming, such as Assembler, C, C++, VisualBasic and Java.
- a user of client computer system 4 operates special software control programs that gather information directed to specific components desired by the user to be installed on the mainframe computer system 2.
- the information is used by the present invention during the automated upgrade processes described herein. After the information gathering processes are complete, a series of processes are invoked in order to perform the mainframe computer operating system upgrade.
- the present invention provides an interface for a client computer system 4 and an existing mainframe computer system 2.
- the present invention preferably queries the existing mainframe computer system 2 for a plurality of parameters that are directed to the way the mainframe computer system 2 is configured.
- the number of volumes and partitions installed on the mainframe computer system 2 is preferably retrieved and stored in a database for use during the upgrade.
- the information gathering component of the present invention uses the information to mimic the existing mainframe computer system 2 environment, and, further, to configure the mainframe computer system 2 that is receiving the upgrade for optimal performance.
- a series of system files are preferably created.
- the system files are formatted as one or more sequential files, and, further, are compressed into one or more smaller-sized files.
- the compressed file(s) are stored on a removable media, for example, a CD-ROM, for future use during the upgrade process.
- the client computer system 4 interprets the files and invokes processes which use the information therein to upgrade the operating system for the mainframe computer system 2.
- a base operating system 2 is provided for the mainframe computer system 2 that comprises many components required of an upgraded mainframe computer operating system.
- the base operating system requires many installation steps, however, preferably provided automatically by the present invention, to combine and customize the components comprising the base operating system in order for a successful LPL to be performed. Absent the steps and processes described herein, a skilled mainframe computer systems programmer is required to enable a mainframe computer system 2, using just the base operating system, to successfully IPL the mainframe computer system 2. The skilled systems programmer is required to combine processes included in the base operating system and, moreover, to provide complex details directed to the mainframe computer system 2 to perform an IPL.
- a series of application processes for example, batch files, are sequentially executed on the mainframe computer system 2 that operate on the base operating system.
- the present invention evaluates output condition codes of each job to verify its successful execution.
- the specific batch job is repeated in order to continue with the upgrade process.
- the upgrade process is halted.
- the first initial program load (“IPL") of the system is performed, and the present invention prompts the user of the client computer system 4 for a series of additional criteria directed to components to be installed on the mainframe computer system 2.
- additional installation measures described in detail below, are performed and a second IPL is preferably done in order to complete the upgrade. Thereafter, the user is able to access the mainframe computer system 4 and enjoy the many benefits of the operating system upgrade.
- the present invention secondarily provides a system and method for adding specific products to the mainframe computer system 2, for example, WEBSPHERE MQ products, easily and quickly.
- a server system for example, a hypertext transfer protocol (“HTTP") server running on the mainframe computer system 2, enables remote access to and use of the information stored in the database 12.
- HTTP hypertext transfer protocol
- a client computer system 4 After a client computer system 4 establishes a communication session, for example a HTTP session, with the HTTP server, the system files directed to the mainframe computer system 4 are preferably transmitted to the client computer system 4.
- the client computer system 4 connects remotely to the server system via a HTTP session, and performs functions directed to the upgrade over the HTTP session.
- step SI 00 the mainframe upgrade system 10 is preferably invoked to discover information directed to a current configuration of the mainframe computer system 2.
- step SI 02 information stored in a RACF database is retrieved for review.
- step SI 04 information directed to the system's LPL is preferably retrieved.
- step S106 a plurality of parameters stored in the mainframe computer system 2 PARMLIB are parsed and stored for future use.
- step S108 the mainframe computer system's 2 Symbol table is retrieved.
- step SI 10 UCB and EDT tables are retrieved.
- step SI 12 the mainframe computer system 2 SYSRES volume information is retrieved.
- step SI 14 the TCP/IP profile and protocol data of the mainframe computer system 2 are parsed and stored for future use.
- step SI 16 hardware information directed to the mainframe computer system 2 is retrieved.
- step SI 18 VTAM members are parsed and stored for future use.
- step SI 20 information directed to all catalogs installed on the mainframe computer system 2 is retrieved.
- step SI 22 the MVS Global Zone on the mainframe computer system 2 is located.
- step SI 24 information directed to Page Data Sets on the mainframe computer system 2 is retrieved and stored for future use.
- step SI 26 UNIX environment information is retrieved.
- step SI 28 Linklist information is retrieved.
- step SI 30 SMS ACS information is retrieved from the mainframe computer system 2 and stored for future use.
- step SI 32 APF information is retrieved.
- step SI 34 all SMP global zones are located.
- step SI 36 LPA list information is retrieved from the mainframe computer system 2.
- step SI 38 system preferably locates all products in SMP-E zone locations.
- step SI 40 the Symbol table is again retrieved.
- the data directed to the above- identified particulars are stored in a discovery database and used to quickly and efficiently configure the environment for the mainframe computer system 2 receiving the upgraded operating system.
- Figures 4(a)-4(d) illustrate the steps associated with an upgrade of an operating system mainframe computer system 2 with an operating system, for example, OS/390 or z/OS in accordance with the present invention.
- the information stored in the discover database including the data retrieved during steps S100-S140 (Fig. 3), is referenced and used during the installation process described in Figures 4(a) -4(d).
- step S200 a user operating the client computer system 4 executes an application to implement the steps associated with the operating system upgrade.
- the application is preferably scaled to run on a desktop PC, and includes instructions to carry out operating system installation processes on mainframe computer system 2.
- step S202 a connection is established between the client computer system 4 and the mainframe computer system 2, for example, by selecting an object, such as a windows icon which invokes software control programs to create the connection.
- the mainframe upgrade system 10 receives information from the user of client computer system 4, for example, user ID, password and EP address defined for a File Transfer Protocol (“FTP") server installed on the mainframe computer system 2, and requests a FTP communication session with the FTP server, for example, by providing the IP address of the FTP server, and the user ID and password information.
- FTP File Transfer Protocol
- step S206 a determination is made whether a FTP server on a mainframe computer system 2 responds to the session request from the client computer system 4. In the event the mainframe computer system 2 does not have an FTP server installed thereon, or the client computer system 4 cannot establish a connection with the FTP server located on the mainframe computer system 2, then the process ends in step S208. In the event that, in step S206, the FTP server on mainframe computer system 2 successfully responds to the client computer system 4 request for a communication session, then, in step S210, mainframe upgrade system 10 preferably generates and maintains information required to authenticate a user on mainframe computer system 2.
- the mainframe upgrade system 10 interacts with other installation and operating system maintenance applications that are inherent to the particular operating system being installed.
- the mainframe upgrade system 10 preferably interacts with SMP-E, an IBM tool for installing and maintaining software in OS/390 or z/OS mainframe computer systems.
- the mainframe upgrade system 10 preferably generates a job card that provides information for SMP-E to implement the setup and installation of the operating on mainframe computer system 2.
- the client computer system 4 transmits the generated job card to the mainframe computer system 2.
- step S212 the present invention prepares the user for proper authorization in order to install and maintain the operating system on mainframe computer system 2.
- the mainframe upgrade system 10 fixes a user ID for proper SECURITY authentication. In the event that an error occurs during the authentication process, then, in step S214, the process terminates.
- the mainframe upgrade system 10 preferably uploads a utility load library into the mainframe computer system 2.
- the mainframe computer system 2 receives the utility load library and installs it into a predefined location on mainframe computer system 2, for example, SYS1.LDSIKLIB.
- mainframe computer system 2 installs the utility load library in step S218, then an evaluation is made whether the mainframe computer system 2 possesses the required settings to continue with the installation process (step S220). In the event the required settings for continuing the installation do not exist, then in step S222, the process terminates.
- a screen display is automatically presented to the user that identifies setting(s) that require correction or adjustment.
- three work files are preferably allocated (step S224). Preferably, the three work files are needed to be used for the compressed files, the uncompressed files and the restore files. In the event that an error occurs when allocating the work files in step S224, then, in step S226, the process terminates.
- a list is preferably generated on the mainframe computer system 2 for the volume serial number ("VOLSER") and also for the upper control blocks (“UCB").
- VOLSER volume serial number
- UMB upper control blocks
- the list of the VOLSER and the UCB's is transmitted, in step S228, to the client computer system 4 and the mainframe upgrade system 10 preferably saves the list in a memory (step S230).
- step S232 the mainframe upgrade system 10 preferably supplies a new master catalog name, VOLSER and UCB address to the mainframe computer system 2.
- the mainframe computer system 2 preferably checks for a unique catalog name for the VOLSER and empties the UCB (step S234). In the event that an error occurs during either reception of the new master catalog name, VOLSER, or during the emptying of the UCB addresses, then the process terminates in step S236.
- step S238 the mainframe upgrade system 10, operating on client computer system 4, supplies generic information directed to a system residence file/disk (SYSRES), VOLSER and UCB to mainframe computer system 2 (step S238).
- step S240 the mainframe computer system 2 checks for the VOLSER uniqueness and corresponding empty UCB's. In the event an error is encountered during the check for VOLSER uniqueness and a corresponding empty UCB, then in step S242, the process terminates.
- step S244 the mainframe computer system 2 receives the generic DISTLIB, VOLSER and UCB and again checks for VOLSER uniqueness and corresponding empty UCB's.
- step S246 the mainframe upgrade system 10 preferably supplies generic distribution libraries (DISTLIB), VOLSER and UCB's to the mainframe computer system 2.
- DISTLIB generic distribution libraries
- Figure 4(b) illustrates the continued steps involved in the process of installing operating system on mainframe computer system 2.
- step S250 the mainframe upgrade system 10 supplies VOLSER and UCB's for the Bookmanager Volume.
- step S252 the mainframe computer system 2 receives the Bookmanager volume information, and checks for corresponding empty UCB's (step S252). In the event an error is encountered during the check for the VOLSER uniqueness and/or corresponding empty UCB's for the Bookmanager volume, then the process terminates in step S254.
- step S256 the mainframe upgrade system 10 supplies a VOLSER and UCB's for the SMP-E volume.
- the mainframe upgrade system 10 checks for VOLSER uniqueness and corresponding empty UCB's therefor (step S258). If an error is encountered during the check for the VOLSER uniqueness and/or the corresponding empty UCB's for the SMP-E volume, then the process terminates (step S260).
- step S262 the mainframe upgrade system 10 provides VOLSER and UCB's information for the JES2 volume.
- the mainframe upgrade system 10 checks for VOLSER uniqueness and corresponding empty UCB's. In the event an error is encountered during the check of the JES2 volume VOLSER uniqueness and corresponding empty UCB's, in step S266, the process terminates.
- step S268 the mainframe upgrade system 10 supplies VOLSER and UCB information for the UNIX volume to the mainframe computer system 2.
- step S270 the mainframe computer system 2, after receiving the UNIX volume VOLSER and UCB information, checks for VOLSER uniqueness and corresponding empty UCB's. In the event that an error is encountered during the checking for the .UNIX volume VOLSER and corresponding empty UCB, then, in step S272, the process terminates.
- step S274 the mainframe upgrade system 10 preferably supplies the SMS volume VOLSER and UCB information to the mainframe computer system 2.
- the mainframe computer system 2 preferably checks for VOLSER uniqueness and corresponding empty UCB's. In the event an error is encountered during the checking for the SMS volume VOLSER uniqueness and UCB, then the process terminates (step S278).
- step S280 the mainframe upgrade system 10 preferably supplies VOLSER and UCB's for page volume.
- step S282 the mainframe computer system 2 receives the page volume information and the mainframe upgrade system 10 checks for VOLSER uniqueness and corresponding empty UCB's.
- step S286 the mainframe upgrade system 10 preferably prompts the user of client computer system 4 for the UCB's for the console. After the user submits the UCB's for the console, the console information is transmitted to the mainframe computer system 2 and the mainframe computer system 2 preferably checks the console UCB's (step S288). In the event that an error is encountered during the check of the console UCB, then, in step S290, the process terminates.
- the mainframe upgrade system 10 preferably provides volume serial numbers and UCB's for a plurality of volumes.
- the mainframe upgrade system 10 preferably reviews all of the parameters that have been entered and provided to this point.
- mainframe upgrade system 10 preferably makes a determination whether any of the parameters transmitted to this point need to be modified. In the event that one or more parameters does need to be modified, then the process loops back to step S244 and continues from there. In the event that no parameters require modification, then the process continues to step S296 ( Figure 4C).
- step S296 the mainframe upgrade system 10 preferably submits an L IT job to the mainframe computer system 2.
- the mainframe computer system 2 receives the INIT job, and, in step S298, initializes the eleven volumes (SYS1.LEKLIB, Master Catalog, Generic Sysres, Generic Distlib, Bookmanager, SMP-E, JES2, Unix, SMS, Page Volume and Console) defined up to this point.
- SYS1.LEKLIB Master Catalog, Generic Sysres, Generic Distlib, Bookmanager, SMP-E, JES2, Unix, SMS, Page Volume and Console
- step S300 the mainframe upgrade system 10 preferably uploads updated catalog volumes to the mainframe computer system 2.
- the mainframe computer system 2 receives the updated catalog volumes, and, thereafter, unzips the volumes and receives a decision support system (DSS) dump to the mainframe computer system 2 prepared by the mainframe upgrade system 10.
- DSS decision support system
- the mainframe computer system 2 operates, for a period of time, independently of the client computer system 4 in order to prepare the catalog volumes for use.
- a new master catalog is defined (step S304)
- a purge data set is defined (step S306)
- SMS data sets are defined (step S308)
- a LOGREC is defined (step S310).
- step S212 a JES2 data set is defined.
- the mainframe computer system 2 preferably restores data sets. For example, in step S314, the mainframe computer system 2 restores the data set from a DSS dump image. Moreover, in step S316, the mainframe computer system 2 preferably restores systems specific hierarchical file system ("HFS") data sets. Following the restoration of the data sets, the mainframe computer system 2, in step S318, checks SYSO.IPLPARM LOADXX numbers. In step S320, the console member is created in SYS0.PARMLIB. And in step S322, the mainframe computer system 2 preferably copies the current IODF to a new system.
- HFS systems specific hierarchical file system
- Figure 4(d) shows the remaining steps involved in upgrading the operating system on the mainframe computer system 2 and prepares for the mainframe computer system 2 automatic IPL.
- step S324 the mainframe upgrade system 10 invokes the client computer system 4 to upload the RES volume 1 and 2 images to the mainframe computer system 2.
- the mainframe computer system 2 preferably receives the updated RES volumes images and decompresses the images to receive DFDFS dump data sets and restore the full volume therefrom.
- the RES volume is created on the mainframe computer system 2.
- the mainframe upgrade system 10 preferably uploads the DIST volumes 1 and 2 images from the client system 4 to the mainframe computer system 2.
- step S332 the DIST volumes images are decompressed, the DFDFS dump data set is received and, in step S334, the DIST volume is created on the mainframe computer system 2.
- step S336 the mainframe upgrade system 10 preferably uploads the book volume images to the mainframe computer system 2.
- step S338, the mainframe computer system 4 decompresses the book volume images, receives DFDFS dump data set and, in step S340, restores the full volume.
- step S342 the Unix volume images are preferably uploaded from the mainframe upgrade system 10 to the mainframe computer system 2.
- step S344 the mainframe computer system 2 preferably decompresses the Unix volume images, receives the DFDFS dump data set, and restores the full volume.
- step S346 the Unix volume is created.
- step S348, the mainframe upgrade system 10 preferably uploads SMP volume images to the mainframe computer system 2.
- step S350 the mainframe computer system 2 preferably decompresses the SMP image, receives DFDFS dump data set and restores the full volume.
- step S352 the SMP volume is created.
- step S354 the mainframe upgrade system 10 submits a job for the mainframe computer system 2 to complete the upgrade of the operating system.
- the VOLSER information is put in a data set, and, in step S358, the mainframe computer system 2 preferably re-catalogs every data set using symbolic names.
- step S360 the mainframe computer system 2 preferably creates IEASYMXX members in PARMLIB.
- the VOLSER information, the re-cataloged data sets and the IEASYMXX numbers in PARMLIB are all placed in the catalog volume.
- step S362 the mainframe upgrade system 10 preferably submits a job that preferably deletes utilities on the mainframe computer system 2 as a clean up process.
- step S364 the submitted job deletes utilities from SYS1.LINKLIB on the mainframe computer system 2.
- Figure 5 A, 5B and 5C identify preferred steps in customizing the newly installed mainframe computer system 2 that has the upgraded operating system installed thereon. For example, adding software products, for example, WEB SPHERE MQ products, to a mainframe computer system 2 is implemented using the preferred steps described below.
- adding software products for example, WEB SPHERE MQ products
- step S366 Figure 5A
- the mainframe computer system 2 is IPL'D.
- step S368 the user of client computer system 4 enters the IP address of the upgraded mainframe computer system 2.
- the mainframe upgrade system 10 preferably receives information from a user directed to installed hardware on the mainframe computer system 2. For example, in step S372, the user identifies a OSA token ring adapter. In step S374, the user identifies an OSA Ethernet adapter. In step S376, the user identifies a CISCO CIP adapter. In step S378, the user identifies QDIO adapter.
- step S372 and S374, respectively the user is preferably prompted to enter a link number (step S380). Thereafter, a UCB interface address is similarly provided (step S382). If, in step S376, a CISCO CIP adapter is identified, then additional information including a host CLAW Name (step S384), and a Host Workstation name (step S386) are preferably provided and, thereafter, the UCB interface address is submitted (step S382).
- step S3708 a QDIO adapter is identified.
- additional information including a Read Address (step S388), a Data Path address (step S390) and a TRLE name (step S392) are submitted by the user to the mainframe upgrade system 10.
- a UCB interface address is provided (step S382).
- step S382 After the UCB interface address is entered (step S382), the user is prompted to enter the console UCB address (step S394). Thereafter, the a 3270 UCB address is provided (step S396) and a TCP/IP Net Mask is entered by the user (step S398).
- step S400 a TCP/IP gateway address is entered.
- the user provides a DNS address
- step S404 a domain name is entered.
- step S406 the user provides a VTAM subarea, a Host name is provided in step S408, and, in step S410, the user submits the time zone where the mainframe computer system 2 is located.
- step S412 the system makes a determination whether the State where the customization process is occurring is either Alaska, Hawaii or Indiana. If, during the customization process, in step S414, a determination is made that the State is not Alaska, Hawaii or Indiana, then a determination is made whether the mainframe computer system 2 is running DST. These are states that handle daylight savings time in a different manner. The user is prompted to submit a customer identification number (step S416). Thereafter, in step S418, determination is made whether to continue with the process, re-enter any of the above-identified parameters, or cancel the process.
- step S420 the process terminates.
- the parameters e.g., the TCP IP gateway, the TCPIP net mask, UCB address, and the like
- step S4108 if the user desires to continue, then SMPE zones are loaded to the SMPE volume (step S422). Moreover, SYSO.PARMLIB members: APPCPMXO, COMMNDXO, CONSOLXO, and IEASYMXO are customized (step S424).
- step S426 the SYSO.VTAMLST members: ATCRUNXX, ATCSTRXX, AXXTSOA, LCLXXTRM, and TCPXXTRM are customized.
- step S430 system items are defined.
- step S432 a plurality of data sets and files are created including the EREP/OLGREC files, HASP ACE, 2 CKPT DATA SETS, and couple data sets are defined.
- SCDS, ACDS and COMMAND DATA SETS are defined. The SCDS is loaded, and the SMS volume is added to the storage group. Moreover, in step S434, SMS is activated.
- step S436 System Specific HFS for shared Sysplex and Update files, and the like are restored.
- step S438 a stand alone dump is submitted, and the system is shut down, and, thereafter, the upgraded mainframe computer system 2 has another IPL performed thereon (step S440).
- the combined processes directed to upgrading a new operating system on a mainframe computer system 2, modifying an existing operating system, or adding new products to an existing mainframe computer system 2 provides significant time and cost savings.
- the skill level of a person who performs a mainframe computer system 2 operating system upgrade and maintenance is able to be significantly lower than for prior art mainframe operating system upgrades. This is due, in large part, because many of the tasks associated with installation, configuration and modification of mainframe computer system 2 operating systems, is performed automatically.
- the present invention preferably reads operating system internal control blocks to assess the entire system. The information received from the assessment is used as a template for changes, upgrades, clones and the like. As changes are made to the environment in the mainframe computer system 2, the otherwise disjointed components that contribute to the overall system are automatically combined, thereby maintaining seamless operations for upgrading the mainframe computer system 2.
- a graphic user interface front end is provided for the user operating client computer system 2, and a plurality of utilities operating in a back end are accordingly provided.
- the knowledge base or inventory of a complete mainframe operating system is preferably maintained. In comparison with prior art software and hardware mainframe installation and upgrade applications, the present invention provides significant benefits, including financial, time and personnel savings.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2500912A CA2500912C (en) | 2002-10-02 | 2003-09-04 | System and method for expediting and automating mainframe computer setup |
AU2003268506A AU2003268506A1 (en) | 2002-10-02 | 2003-09-04 | System and method for expediting and automating mainframe computer setup |
EP03749473A EP1552386A4 (en) | 2002-10-02 | 2003-09-04 | System and method for expediting and automating mainframe computer setup |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/263,972 US7194737B2 (en) | 2002-10-02 | 2002-10-02 | System and method for expediting and automating mainframe computer setup |
US10/263,972 | 2002-10-02 |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2004031890A2 WO2004031890A2 (en) | 2004-04-15 |
WO2004031890A3 WO2004031890A3 (en) | 2004-06-03 |
WO2004031890A9 true WO2004031890A9 (en) | 2004-07-22 |
Family
ID=32042116
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/027935 WO2004031890A2 (en) | 2002-10-02 | 2003-09-04 | System and method for expediting and automating mainframe computer setup |
Country Status (5)
Country | Link |
---|---|
US (2) | US7194737B2 (en) |
EP (1) | EP1552386A4 (en) |
AU (1) | AU2003268506A1 (en) |
CA (1) | CA2500912C (en) |
WO (1) | WO2004031890A2 (en) |
Families Citing this family (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2451164C (en) * | 2003-09-11 | 2016-08-30 | Teamplate Inc. | Customizable components |
CA2443454A1 (en) * | 2003-09-11 | 2005-03-11 | Teamplate Inc. | Data binding method in workflow system |
US8689185B1 (en) * | 2004-01-27 | 2014-04-01 | United Services Automobile Association (Usaa) | System and method for processing electronic data |
US20050235281A1 (en) * | 2004-04-19 | 2005-10-20 | Telefonaktiebolaget L M Ericsson (Publ) | Combined software installation package |
US7503041B2 (en) * | 2004-07-01 | 2009-03-10 | International Business Machines Corporation | Apparatus, system, and method for delivery of software |
US7797698B2 (en) * | 2004-11-17 | 2010-09-14 | International Business Machines Corporation | Method and apparatus for dynamic middleware assembly |
US20060248513A1 (en) * | 2005-04-27 | 2006-11-02 | Foster Gavin A E | z/OS rapid automated deployment method |
US8429527B1 (en) | 2005-07-12 | 2013-04-23 | Open Text S.A. | Complex data merging, such as in a workflow application |
US7480643B2 (en) * | 2005-12-22 | 2009-01-20 | International Business Machines Corporation | System and method for migrating databases |
WO2008113641A1 (en) * | 2007-03-19 | 2008-09-25 | International Business Machines Corporation | A method for logging of a remote control session |
US9454384B2 (en) * | 2007-07-05 | 2016-09-27 | Microsoft Technology Licensing, Llc | Custom operating system via a web-service |
US20090089779A1 (en) * | 2007-09-28 | 2009-04-02 | Evelyn Thompson Brengle | Apparatus system and method for customizing a computing environment |
US9395972B2 (en) * | 2011-05-31 | 2016-07-19 | Red Hat, Inc. | Customizing an operating system installer via a web-based interface |
US20130117739A1 (en) * | 2011-11-09 | 2013-05-09 | Ford Global Technologies, Llc | Electronic Tool for Automatically Programming a Plurality of Control Modules in a Vehicle On-Board Computer System |
CN103365667B (en) * | 2012-03-26 | 2018-01-26 | 联想企业方案(新加坡)有限公司 | A kind of method and apparatus of the installation operation system in host computer system |
DE102012103023A1 (en) * | 2012-04-05 | 2013-10-10 | Krones Ag | Device for sterilizing containers e.g. plastic bottles in beverage manufacturing industry, has control device whose image pickup device receives image of exit region in which charge carrier emerges from chamber |
US9110755B2 (en) * | 2012-08-10 | 2015-08-18 | Microsoft Technology Licensing, Llc | Aggregation of update sets |
US8949815B2 (en) | 2013-05-31 | 2015-02-03 | Microsoft Corporation | Driver installation for targeted and non-present devices |
US9317538B1 (en) * | 2013-09-10 | 2016-04-19 | Ca, Inc. | Methods for generating data sets using catalog entries |
US9304887B2 (en) | 2013-09-16 | 2016-04-05 | International Business Machines Corporation | Method and system for operating system (OS) verification |
CN104038922B (en) * | 2014-05-07 | 2017-09-01 | 小米科技有限责任公司 | File synchronisation method and relevant apparatus |
WO2016008256A1 (en) * | 2014-07-15 | 2016-01-21 | 深圳市金立通信设备有限公司 | Method for terminal to update operating system, terminal and system |
US10802878B2 (en) * | 2017-03-31 | 2020-10-13 | Bmc Software, Inc. | Phased start and stop of resources in a mainframe environment |
US11088923B2 (en) | 2019-06-19 | 2021-08-10 | International Business Machines Corporation | Multi-stage authorization |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0792744B2 (en) * | 1990-08-20 | 1995-10-09 | インターナショナル・ビジネス・マシーンズ・コーポレイション | A method of installing multi-level application software on a data processing device. |
US5499340A (en) * | 1994-01-12 | 1996-03-12 | Isogon Corporation | Method and apparatus for computer program usage monitoring |
US5862308A (en) * | 1996-12-03 | 1999-01-19 | Bull Hn Information Systems Inc. | Fault intercept and resolution process independent of operating system |
US6026238A (en) * | 1997-08-18 | 2000-02-15 | Microsoft Corporatrion | Interface conversion modules based upon generalized templates for multiple platform computer systems |
US6167408A (en) * | 1998-08-31 | 2000-12-26 | International Business Machines Corporation | Comparative updates tracking to synchronize local operating parameters with centrally maintained reference parameters in a multiprocessing system |
US6389591B1 (en) * | 1998-09-03 | 2002-05-14 | Microsoft Corporation | Method and apparatus for determining preferred controls for an upgradable operating system |
US6378128B1 (en) * | 1998-10-08 | 2002-04-23 | Microsoft Corporation | System and method for dynamically modifying an install-set |
US7266818B2 (en) * | 2002-06-28 | 2007-09-04 | Microsoft Corporation | Automated system setup |
-
2002
- 2002-10-02 US US10/263,972 patent/US7194737B2/en not_active Expired - Lifetime
-
2003
- 2003-09-04 EP EP03749473A patent/EP1552386A4/en not_active Withdrawn
- 2003-09-04 CA CA2500912A patent/CA2500912C/en not_active Expired - Fee Related
- 2003-09-04 AU AU2003268506A patent/AU2003268506A1/en not_active Abandoned
- 2003-09-04 WO PCT/US2003/027935 patent/WO2004031890A2/en not_active Application Discontinuation
-
2005
- 2005-07-18 US US11/183,386 patent/US8042107B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
CA2500912C (en) | 2012-08-21 |
US7194737B2 (en) | 2007-03-20 |
EP1552386A4 (en) | 2007-10-10 |
WO2004031890A3 (en) | 2004-06-03 |
CA2500912A1 (en) | 2004-04-15 |
US20040068722A1 (en) | 2004-04-08 |
AU2003268506A8 (en) | 2004-04-23 |
EP1552386A2 (en) | 2005-07-13 |
US8042107B2 (en) | 2011-10-18 |
WO2004031890A2 (en) | 2004-04-15 |
AU2003268506A1 (en) | 2004-04-23 |
US20050268295A1 (en) | 2005-12-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2500912C (en) | System and method for expediting and automating mainframe computer setup | |
US6026438A (en) | Dynamic workstation configuration processor | |
US6898705B2 (en) | Automatic appliance server re-provision/re-purposing method | |
EP1978672B1 (en) | Method for implementing management software, hardware with pre-configured software and implementing method thereof | |
US8458658B2 (en) | Methods and systems for dynamically building a software appliance | |
US6922831B1 (en) | Method and system for providing software utilizing a restore medium and a network | |
US20020112232A1 (en) | System and process for building host computers | |
US7302558B2 (en) | Systems and methods to facilitate the creation and configuration management of computing systems | |
US8935687B2 (en) | Incrementally updating a software appliance | |
US8943496B2 (en) | Providing a hosted appliance and migrating the appliance to an on-premise environment | |
US7426052B2 (en) | System and method for remotely building an information handling system manufacturing image | |
US7146612B2 (en) | Method and system for receiving a software image from a customer for installation into a computer system | |
CN100399268C (en) | Computer system not relying on operation system renewing software data and method | |
US20090300593A1 (en) | Methods and systems for managing a software appliance | |
US20040025155A1 (en) | Method, computer program product, and system for configuring a software image for installation into a computer system | |
US20070124189A1 (en) | Sustaining a fleet of configuration-controlled assets | |
JPH0792744B2 (en) | A method of installing multi-level application software on a data processing device. | |
CN101004689A (en) | Method and system for automated installation of system specific drivers | |
US8103863B2 (en) | Workflow management to automatically load a blank hardware system with an operating system, products, and service | |
US8272000B2 (en) | System and method for abstracting computer disk image cloning capabilities from bootable media | |
US8631103B1 (en) | Web-based administration of remote computing environments via signals sent via the internet | |
US11841838B1 (en) | Data schema compacting operation when performing a data schema mapping operation | |
US20030046372A1 (en) | System, apparatus, and method to configure a server in the field | |
JP2001249801A (en) | Software installation device and storage medium | |
Chen | New Development of Storage Architectures and Network Managed PCs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
COP | Corrected version of pamphlet |
Free format text: PAGES 1/10-10/10, DRAWINGS, REPLACED BY NEW PAGES 1/10-10/10 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2500912 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003749473 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2003749473 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |