Topics Map > University of Chicago > IT Services > Business Systems > Mainframe
Mainframe - 1999 OS/390 Upgrades
This article provides a history of upgrades to the 1999 OS/390 mainframe.
On Sunday morning, 8/22/99, we failed to test the installation of CICS TS SVC, CICS TS Linkpack Library, and CICS TS Linklist Library. Due to a programming error, these components were not available between 9:00 and 11:00 AM. Another full-scale transaction test has been scheduled for Sunday, 8/29/99, from 9:00 AM until 11:00 AM.
During System Test Time on Tuesday, 8/24/99, CICS was brought up with the new link library and LPA and the new SVC. The upgrades were backed out at the end of Test Time. We arranged another opportunity for transaction testing on Friday morning, 8/27, during morning System Test Time.
During System Test Time on Friday, 8/27/99, we brought up CICS with the new CICS TS Linklist and Linkpack Libraries. Limited testing was done successfully in preparation for larger scale Computing Partner testing of CICS transactions on Sunday, 8/29/99. The upgrades were backed out at the end of Friday morning’s Test Time.
On Sunday morning, 8/29/99, we tested the installation of CICS TS Linkpack Library, and CICS TS Linklist Library. These “downward compatible” components were available between 9:00 and 11:00 AM. Computing Partners tested their CICS transactions during this time.
The new CICS components were left in place following Test Time. This will facilitate the transition to CICS Transaction Server, currently scheduled for December 1999.
Also during Sunday morning Test Time, 8/29/99, we applied a number of OS/390 modifications that had been on hold:
- ESP maintenance that had been deferred for a couple of months
- A modification to Output Master to change the way PRMODE and DUPLEX are used to request duplex printing
- A modification to allow TSO users to access a secondary JES2 which could be available for testing as early as mid-September
- Installation of the latest version of MVS/Quickref
During System Test Time on Thursday, 9/2/99,we successfully tested the System Logger with CICS Transaction Server active. System Logger and CICS TS were removed at the end of Test Time. CICS Transaction Server is scheduled for installation in December 1999. System Logger is a requirement of CICS Transaction Server.
During System Test Time on Friday, 9/3/99, we successfully started the System Logger subsystem. We then started the Production version of a CICS Online, which came up without any problems, demonstrating that CICS 3.3.0 systems will run in Production without interference from the System Logger. System Logger was removed at the end of Test Time.
As a result of Central Servers and Mainframes’ effort to ready the IBM OS390 Mainframe System for Y2K testing and compliance, we uncovered much obsolete and unused software. These items included almost everything which had been cataloged under SYS2. During System Test Time on Sunday morning, 9/5/99, we eliminated such software from the IBM OS390 Mainframe.
Also during Test Time on 9/5/99, we moved SAS, SCRIPT, XICS, HFDL, and XREFPLUS from SYS2 to the SYS5/UOC1 file structure. All PROCs, TSO CLISTs, ReXX EXECs, TSO HELP files, and ISPF dialog supports for those systems were moved to SYS5/UOC1. This involved extensive renaming and recataloging of files.
Anyone using the standard cataloged procedures and CLISTs (and anyone overriding the same in standard ways) should not experience a problem with this move. However, anyone who has made a private SAS PROC will be affected and should contact Jim Lichtenstein at (773) 702-7615.
We brought up System Logger during Test Time and it was left active in the Production LPAR once Test Time was over. System Logger has had no negative impact on the Production LPAR. When CICS Transaction Server is installed in December 1999, it will require that System Logger be an active subsystem.
Our current SPSS license expired at the end of August. We removed SPSS from the IBM OS/390 Mainframe during Test Time on Sunday, 9/5/99. If you have a continuing need for SPSS, the Campus Computer Store has site license pricing available.
During System Test Time on Sunday, 9/12/99, we installed a new ACF LogonID Field Definition Record, which removed obsolete, locally defined fields and added new fields required for CICS Transaction Server. This update will not affect anyone's ability to log on and do their work. One CICS Online Database was successfully brought up as a test.
System Logger, another CICS TS requirement, was made a permanent subsystem. System Logger has been active since Test Time on 9/5.
We did some work in preparation for the new JES2 which we hope to have available as a secondary, testable subsystem in the near future.
During System Test Time on Sunday, 9/26/99, we did some internal testing of Maintenance which will be required by the new IBM 9393 DASD. This Maintenance will not be applied to the Production system until full Open Testing (scheduled for Sunday, 10/3/99) can be completed successfully.
We made some modifications to ACF2 records in preparation for CICS Transaction Server. These modifications will not affect anyone’s ability to log in to the Mainframe and do their work.
We installed XREFPLUS 3.3M, the Y2K compliant version which replaces XREFPLUS 2.4G in Production. We have already successfully tested the ISPF interface panels but should anyone have problems using XREFPLUS 3.3M in batch processing, please contact Jim Lichtenstein at 2-7165 for assistance.
During System Test Time on the IBM OS/390 Mainframe on Tuesday, 9/28/99, we did some internal testing of Maintenance which will be required by the new IBM 9393 DASD. This Maintenance will not be applied to the Production system until full Open Testing (scheduled for Sunday, 10/3/99) can be completed successfully.
During System Test Time on Thursday, 9/30/99, we tested (but did not install) System Maintenance which will be required by the new DASD. Open Testing of the maintenance in the Production LPAR has been scheduled for Sunday, 10/3/99, from 9:00 AM until 12:00 Noon (during System Test Time scheduled to run from 7:30 AM until 1:00 PM). We also installed a new hardware configuration designed to include the new IBM 9393 DASD. Tests were run, demonstrating that the system performed correctly with the new configuration installed. The new configuration was left in place. (The old configuration is still available if needed.)
New DASD: We have taken delivery of the IBM 9393-X82 DASD for Mainframe storage. Following CSM’s internal testing, migration of data to the IBM 9393 should begin during System Test Time on Sunday, 10/24/99. We will have sufficient storage capacity to clone our entire Production environment to a separate LPAR to facilitate Y2K testing of mainframe applications. This LPAR should become available sometime in early November.
We scheduled System Test Time on Sunday, 10/3/99, from 7:30 AM until 1:00 PM. The time from 9:00 AM until 12:00 Noon was reserved for Open Testing in the Production LPAR of the System Maintenance which will be required by the new DASD array. During that time, several CICS Online Regions and two M204 Online Regions were made available. Several problems were reported; all were resolved during the test period with one exception: Expediter TSO returned ABEND SOC1 while compiling a CICS program. This error will be investigated during the next week but should not interfere with applying the System Maintenance in Production on Sunday, 10/10.
During System Test Time on Sunday, 10/10/99, the System Maintenance required for the new DASD array was installed in the Production LPAR following successful Open Testing on Sunday, 10/3/99.
In response to a reported problem with Expediter/TSO compiles not working properly, maintenance was applied in Compuware Shared Services where the COBOL compiler support is located.
During System Test Time on Tuesday morning, 10/19/99, we reconfigured the IBM OS390 System to allow for full use of the IBM 9393 DASD array which currently contains only Test Volumes. Plans for Production use of the new DASD will be announced soon.
During extended System Test Time on Sunday, 10/24/99, we applied additional maintenance on the Production System in support of the IBM 9393 DASD array. We also installed “SnapShot” software which will allow us to utilize the disk-copying capabilities of the new DASD for backup and 3rd LPAR purposes. The System Maintenance and SnapShot had been active on our internal Test LPAR. Finally, we migrated our Operating System and WORK0x disk volumes to the new DASD array as Production volumes. We did not move any User data on Sunday, 10/24. We will not change any Production volume names at any stage of the migration process. If all goes well with the new DASD, we may begin to migrate the balance of Production disks as early as morning Test Time on Tuesday, 10/26.
During System Time on Tuesday, 10/26/99, we migrated theSPILL1 and all nine ADM00x volumes to the new IBM 9393 DASD array. No volume names were changed. Our data set pooling rules are based on volume names and have not be affected by the migration of volumes to the new DASD. Our next (and last) set of moves has been tentatively scheduled for morning Test Time on Thursday, 10/28/99.
An emergency IPL was performed on the OS390 Mainframe system at about 9:45 AM on Wednesday, 10/27/99, to correct a shortage of Real Storage space preventing anyone from logging in to TSO. Access to online databases was not affected. Real Storage space was freed by bringing up the Mainframe without the secondary JES which was being tested in the Production LPAR. After evaluating our resource allocation on the Mainframe, we will decide on when to reinstate the secondary JES. One other effect of the unscheduled IPL was the disabling of the IBM 7171, an ASCII to 3270 protocol converter used to access the IBM OS/390 Mainframe via the dial-up line (773)753-0975. IBM no longer maintains the 7171 and will not certify this equipment as Y2K compliant. The removal of the 7171 had been staged to take place during the IPL following Test Time scheduled for Thursday morning, 10/28/99. A network connection and a TN3270 client should be used to access the Mainframe.
During System Test Time on Thursday morning, 10/28/99, we migrated the nine FIN00x and the six YR2Kx volumes to the IBM 9393 DASD array. No volumes names were changed. Pooling rules were not affected. No data has been deleted from the EMC volumes which have been renamed. This move completes the migration of Production volumes from EMC to IBM.
During System Test Time on Sunday, 10/31/99, we applied emergency maintenance which we hoped would correct the problem we have been experiencing with long delays accessing TSO at certain times of the day. However, as of Monday morning, 11/1/99, the problem persisted, blocking TSO logins from 8:00 AM until 9:00 AM.
We continue to experience long delays accessing TSO between 8:00 AM and 9:00 AM. Systems personnel are investigating this ongoing problem. Please watch this page for updates.
The IPLs on Tuesday, 11/2/99, and Wednesday, 11/3/99, had no apparent affect on the delays in accessing TSO during certain times of the day. We had modified a parameter which limits the number of concurrent activities on the system and relocated OPS/MVS log and checkpoint data sets to non-paging volumes without affecting the TSO access delays.
During System Test Time on Thursday, 11/4/99, we did some preparation for the pre-production LPAR, now called UCHIBETA. Test Time was followed by an IPL of the OS/390 System to implement some modifications to OPS/MVS. These modifications were apparently successful in relieving the long delays associated with accessing TSO at certain times of the day.
The new Y2K-compliant version (2.5) of JES2 was made available for testing on the Production System as a secondary JES2 (named JESA). We worked with applications programmers to test Production jobs.
Access to JESA was possible by replacing the string IKJACCNT with $JESA under the PROCEDURE===> prompt on the Time Sharing Option Logon Parameters screen and continuing logon as normal.
It was possible to have jobs submitted under JES2 run under JESA by including the line /*ROUTE XEQ L1S2JES2 before the first EXEC statement in the JCL.
It was also possible to have jobs submitted under JES2 print under JESA by including the line /*ROUTE PRINT L1S2JES2 before the first EXEC statement in the JCL.
Both lines could appear in the same job.
Following this week of successful testing of JES2 2.5, it was installed as Production during Test Time on Sunday, 11/14/99. Please NOTE that the above instructions will no longer work following the installation of JES2 2.5 on Sunday, 11/14. Please communicate any problems encountered with JES2 2.5 to Helen Seren at email@example.com so that problems may be addressed immediately.
During System Test Time on Friday, 11/12/99, we did preparation work on the UCHIBETA LPAR to allow the use of round-reel (3420) tape drives.
CICS Transaction Server (CICS TS) will replace the current version of CICS in Production. We held a seminar for interested parties to demonstrate the differences between the current CICS and the Y2K-compliant CICS TS on Friday, 11/12/99.
During System Test Time on Sunday, 11/14/99, we installed the Y2K-compliant JES2 2.5 as the Production default. All pending jobs were completed and all queues were cleared. A Cold Start was performed at the end of Test Time.
DBFSY2K was converted to CICS TS (Transaction Server) 1.3 and has beeen active on the Production LPAR since Monday, 11/15/99. A CICS TS 1.3 version of DBCOAS should be made available on the UCHIBETA LPAR later that week.
The problem we had been experiencing on the IBM OS/390 Mainframe with IOF not recognizing the SCOPE parameter on the IOF User Option Menu was solved.
We scheduled System Test Time for Sunday, 11/21/99, to do some general system testing.
During scheduled System Test Time on the IBM OS390 Mainframe on Sunday, 11/28/99 we made successful preparations to provide printer service on the UCHIBETA LPAR.
The Mainframe LPAR capable of containing a clone of the Production system (a.k.a. the “3rd LPAR” but officially UCHIBETA) will be available for Open Testing starting 12/2/99. A Testing Schedule Table will be maintained.
During scheduled System Test Time on the IBM OS/390 Mainframe on Friday, 12/3/99, we corrected the problem with setting up all disks to be copied from UCHIMVS1 which had delayed availability of UCHIBETA on 12/2/99.
We scheduled System Test Time on the IBM OS/390 Mainframe on Sunday, 12/5/99, for general system work including extending our license for Output Master into the Year 2000. Availability of the UCHIBETA LPAR was delayed until 12:00 Noon so that this update could be reflected there.
During scheduled System Test Time on Thursday, 12/9/99, we physically disconnected the IBM 7171 Protocol Converter from the Mainframe. The 7171 had not been in use since the end of October.
During System Test Time on Sunday, 12/12/99, we installed the Y2K Compliant SAS TS Level 470 as the Production Default on both UCHIMVS1 and UCHIBETA.
During System Test Time on Tuesday, 12/14/99, we installed CICSMGR 5.3 in support of CICS TS. Also, all CICS Regions are now running CICS TS.
System Test Time was scheduled for Sunday, 12/19/99, from 7:30 AM until 11:00 AM. This delayed availability of the UCHIBETA LPAR until 11:00 AM.
Our homegrown resource tracking and reporting BJACS jobstream was not Y2K ready. Date and Dollar fields in job logs and Logoff messages have been frozen as of 12/27/99 until a new BJACS stream can be designed.
Activity information in ISPF L.DET (Detail Reports) is unavailable and L.DET has been disabled.
We will continue to capture resource and activity data which will be processed in March, 2000, our target for new BJACS jobs.
During System Test Time on Wednesday, 12/29/99, we installed the new Y2K-compliant version of the Accounting Master Data Base (AMDB). The new AMDB will now be active in both the UCHIMVS1 and UCHIBETA LPARs.