Best way to test upgrade TLMS to 14.0.
search cancel

Best way to test upgrade TLMS to 14.0.

book

Article ID: 135486

calendar_today

Updated On:

Products

TLMS Tape Management

Issue/Introduction

Upgrading TLMS to 14.0 Is there a check list for the TLMS 12.0-14.0 conversion?

Environment

Release : 14.0

Component : CA TLMS Tape Management

Resolution

1). Update TLMSIPO from 12.0 to 14.0.

 

2). Update CAS9.

 

A). Delete DO53INIT and YD53INIT from CAIRIMPARM.

 

B). Change TLMS init cards within CAIRIMPARMs.

 

PRODUCT(CA-TLMS/MVS) VERSION(TLE0) INIT(TLE0INIT) PARM(INIT)

 

C). Check that CAS9 is pointing to the correct/updated TLMSIPO

 

D). No change to LMP keys.

 

E). Check that CAS9 has the following:

 

//TLMSOPTS DD DSN=YOUR.CTAPOPTN(&IPO),DISP=SHR 

 

//CTSOPTNS DD DSN=YOUR.CTAPOPTN,DISP=SHR

 

3). Update LINKLST and APF library if needed.

 

4). OAM Interface - Set ROBSCR to YES in TLMSIPO.

 

5). VMF. Iebgener over. BACKUP/RESTORE VMF.

 

6). VMF INDEX. Create new index after VMF backup/restore.

 

7). ALOG. IEBGENER ALOG over.

 

8). RMF. Run conversion upgrade to new format.

 

9). Program TLMSRPTS was been dropped in the 14.0 release. Watch for S806 abends on reports and commands. I have a program to read SMF data and will report who has used the program in the last 30 days.

 

10).New CLIST for TLMS ISPF. Update new CLIST and move into CLIST library.

 

11). Remember to change any PROC's with new library names if you used new names.

 

12). POST-INSTALL.

 

A).Run PROC CATVMFV. This is a new chaining error report that reports on multiple DSN chaining errors. This is new in TLMS 12.6/14.0.

 

B). Verify that all reports have the release number of 14.0 in header.

 

C). Check TLMS ISPF and hit the OPTION panel. Make sure it's release is 14.0.

 

D). Have operations verify the next run of CATTRS. Make sure the movement and scratch totals are in-line. 

 

E). Run a quick IEBGENER tape job. Make sure the VMF is updated correctly.

 

F). OAM interface check. Scratch the volume you just created. Verify in TLMS and OAM that the volume is scratch in both locations. This will verify that

 

OAM/TLMS interface is working.