University of Missouri System

Columbia | Kansas City | Rolla | St. Louis

Skip to content

University of Missouri

Systems and Operations

Announcements

Mainframe Hardware Upgrade (11/14/2003)

 

Mainframe Hardware Upgrade Planned

During the Fall Semester 2003 registration in August the existing mainframe was not able to handle the peak registration activity. This created a particularly bad experience for the Columbia campus. A group was formed to study these problems and make recommendations for their correction.

The Project Team recommended a two-step approach to meeting the above goal prior to the peak registration period for the Winter 2004 Semester which occurs in early January 2004.

 

  1. Offload the TN3270 functions for all mainframe users to the 7507 router and offload all SSL to the content manager switch. It is estimated that this will reduce the mainframe load by 10 – 15%. This step was completed prior to the pre-registration period beginning the third week of October.
  2. Replace the current 120 MIPS 7060-H50 mainframe with a 160 MIPS 2066-0X2 system.

 

The first item was completed prior to the October registration period.

The second item has been approved and is being planned at this time. The new system is to be operational no later than December 28, 2003 in preparation for the January registration period.

Replacing the current processor with the new processor will require some other major equipment and software changes.

 

Hardware Upgrade Overview

There are two major hardware issues that must be addressed before the mainframe can be replaced.

  1. The current system contains about 40% of our disk storage internally. The data on this disk must be moved to an external device before the system can be replaced. Our current external disk does not have space available for this data.
  2. Our current CART drives cannot be directly attached to the new processor.

 

There are software considerations that must be evaluated before any upgrade can be done.

  1. The current production operating system (z/OS 1.1) will need service to run on the new processor.
  2. The need for this hardware upgrade occurred during our implementation of a new version of the operating system. (z/OS 1.4). The hardware upgrade must be completed prior to our original target date for implementing the new operating system. However, if the updates to the z/OS 1.1 system are more difficult than migration to the z/OS 1.4 system, the 1.4 migration date may be moved. This could occur as early as November 30. 2003.

 

The new processor will have features that we will exploit to provide additional performance improvements. For example, the new processor will have two additional network interfaces. All network traffic to the current processor goes thru one interface. All terminal (TN3270), file transfer, email and other traffic now goes thru the Cisco 7507 Router. On the new processor, the terminal (TN3270) traffic will remain on the Cisco router and all other IP traffic will use a new network interface.

 

Disk Replacement

An IBM Enterprise Storage Server (ESS) with 840Gb of storage has been ordered to replace all current disk. Data on the internal disk must be migrated first. This must be done before any meaningful testing can be done on the new processor.

The data from the external disk will also be migrated to the new disk, but this does not have to be complete prior to December 28, 2003.

This upgrade will require the end of 3380 disk support. Two 3380 volumes remain in use. All other 190+ volumes are 3390 format. The remaining users of 3380 disk have been notified individually.

 

Tape Replacement

All current CART (3480) tape used by batch jobs will be replaced with 3490E technology. (Eight 3490-C22 drives)

3480 technology records about 200Mb of data (uncompressed) on a tape using 18 data tracks. 3490E technology doubles the capacity of the tape using 36 data tracks. The general rules for 3480 to 3490E conversion and interchange are:

  1. 3490E drives can read both 18 and 36 track tapes
  2. 3480 drives use ONLY 18 track tapes for read or write
  3. 3490E write ONLY 36 track tapes
  4. A tape cannot contain both 18 and 36 track data
  5. 3490E drives cannot be used to add data to 18 track tapes

 

Pool Tapes (Pnnnnn volumes)

3490E drives can READ our current tapes. When a scratch tape is first used on a 3490E drive, it will be converted to 36 track automatically. Once written on the new drives, tapes become unreadable by the old drives. Because of this, the new drives will completely replace the old drives at the conversion time. No JCL changes should be required to move production jobs to the new drives, with the possible exception of jobs that add data to existing tape volumes or existing tape files. This might be done using DISP=MOD to add to a file or adding additional files to a existing master tape. For these jobs, a new tape volume will need to be started at the time of the 3490E conversion.

 

Private Tapes (Vnnnnn volumes)

We have no way of knowing what techniques are being used to process V-Series tapes. The rules above apply to V-Series tapes as well as to any foreign tape in the library being used for output.

We still encourage users of V-Series tapes to convert to pool tapes (P-series). Support for problems resulting from the use of V-Series tapes will handled at a lower priority than other problems.

 

3480 Data Exchange

We will retain 4 of our current 3480 drives for an undetermined period of time for any data exchange need. The new drives can READ any 3480 or 3490E tape we might receive, but if we need to send data somewhere that is limited to 3480 drives, the old drives will be needed. JCL changes will be needed to access the 3480 drives after conversion to the new drives.

 

Upgrade Sequence and Preliminary Schedule

This is the planned sequence of events by start date. The duration of each event is noted. The sequence of completion is not necessarily the same as the start sequence.

  1. Install new disk (ESS) connected to the current system. Migration of internal disk data must be complete before 2066-0X2 testing.
  2. Install software support for the new hardware on the production system on November 23, 2003.
  3. Install new z/OS version 1.4 on production on November 30, 2003.
  4. Install the 2066-0X2 for testing. After initial checkout, the UMMVSG TEST system will be moved to the new processor. Installation estimate is December 2, 2003. UMMVSG should be on the new processor by December 8, 2003.
  5. Install new tape (3490-C22) and implement in production. Four 3480 drives will be retained for data exchange and remove eight 3480 drives. This schedule is not yet available.
  6. Move the 2066-0X2 to production on December 14, 2003 with a fall back date of December 28th.
  7. Complete migration of data from the current external disk to the ESS by February 15, 2004.

 


Contact webmaster@umsystem.edu. Reviewed May 14, 2008.
Copyright © 2003-2008 The Curators of the University of Missouri. DMCA and other copyright information.