Migrating TSS from 14.0-15.0 on 2 LPars with shared SECFILE.
Article ID: 38022
Updated On:
Products
Issue/Introduction
The scenario described: migrating TSSMVS from r14.0 to TSSMVS r15.0 on a Production System with two LPars where the Security File is shared.
So, to answer the following:
1.) Is it possible to migrate one LPar to r15.0 and then the other LPar?
ANSWER - Yes, but if you're going to share the Security file, then my answer to (2) below is very important and must be followed.
2.) Is it possible to have the Security File shared between these two LPar, where one is on TSSMVS r15.0 and the other is on TSSMVS r14.0?
ANSWER - Yes. but TSSMVS r14.0 needs to be using the VSAM Companion File as well as the Security File (BDAM).
You can share the Security Files between TSSMVS r14 and TSSMVS r15, but TSSMVS r15.0 requires the TSSMVS r12.0, and later, VSAM structure. So if the Security Files were last formatted in a release prior to TSSMVS r12.0, then they will need to be reformatted in order to share.
If TSSMVS r14.0 is not using the new VSAM Companion File, then to create this, the entire Job is in member VSAMDEF3 in the CAIJCL0 dataset, and looks similar to the following. Please be aware that the Dataset Names may be different in your environment as the example below is from a local installation at CA:
=================================================================================================
//Jobcard
//*VSAMDEF3 JOB
//* *****************************************************************
//* CA TOP SECRET (15.0) *
//* COPYRIGHT (C) 1991, 2004, 2005, 2008, 2010 *
//* COMPUTER ASSOCIATES INTERNATIONAL, INC *
//* *
//* MEMBER: VSAMDEF3 *
//* FUNCTION: ALLOCATE VSAM SECFILE EXTENSION *
//* *
//* REPLACE 'CAI.TSS150' WITH INSTALLATION APPROPRIATE QUALIFIERS *
//* *
//* REPLACE 'XXXXXX' WITH INSTALLATION VOLUME SERIAL NUMBER *
//* *
//* *
//* NOTE: RUN STEP2 ONLY IF: *
//* THE SECFILE IS SHARED. *
//* THE SECFILE IS CREATED WITH OPTION "INITVSAM=DIGICERT" *
//* *
//* *****************************************************************
//STEP1 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE FR52M.KOF0SP00.VSAMFILE
DEFINE CLUSTER -
(NAME(FR52M.KOF0SP00.VSAMFILE) -
SHR(3,3) -
RECORDSIZE(256 24576) -
CYLINDERS(1,1) -
SPANNED -
KEYS(64,0) -
VOL(TSO52B)) -
DATA -
(NAME(FR52M.KOF0SP00.VSAMFILE.DATA) -
CISZ(4096)) -
INDEX -
(NAME(FR52M.KOF0SP00.VSAMFILE.INDEX) -
CISZ(4096)) -
CATALOG(ICF.VMVXE52)
/*
//
//STEP2 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE AIX -
(NAME(CAI.TSS150.AIX) -
RELATE(CAI.TSS150.VSAMFILE) -
SHR(3,3) -
RECORDSIZE(256 24576) -
TRK(2,2) -
UPGRADE -
KEYS(08,120) -
VOL(XXXXXX)) -
DATA -
(NAME(CAI.TSS150.AIX.DATA) -
CISZ(4096)) -
INDEX -
(NAME(CAI.TSS150.AIX.INDEX) -
CISZ(4096)) -
CATALOG(ICF.CATALOG)
DEFINE PATH -
(NAME(CAI.TSS150.PATH) -
PATHENTRY(CAI.TSS150.AIX)) -
CATALOG(ICF.CATALOG)
=================================================================================================
You must implement the VSAM Companion File with TSSMVS r14.0 before you start sharing Files with TSSMVS r15.0. Please refer to the 'Convert SDT Records to VSAM' section in the 'CA Top Secret r14 Installation Guide', for the required steps. Also, you can implement the VSAM Companion File without an IPL, just re-start TSSMVS with a REINIT, i.e.:
S TSS,,,REINIT
For more information on setting up the VSAM Security File Extension:
- For TSSMVS r15.0, see the 'TSSMVS r15.0 Installation Guide', chapter 7, section titled 'Creating the Security File', subsection titled 'Create the VSAM File' and Appendix A, section titled 'Convert SDT Records to VSAM'
- For TSSMVS r14.0, see the 'TSSMVS r14.0 Installation Guide', chapter 4, section titled 'Create the Security File', subsection titled 'Create the VSAM File (Optional)' and Appendix B, section titled 'Convert SDT Records to VSAM'.
If you are already sharing the SECFILE (BDAM) and using a VSAM Companion File, you will also need to create the AIX File which is also mentioned in the 'Installation Guide' under 'Creating the SECFILE' section.
If you use TSSMVS r14.0 to set up the VSAM Security File, once the VSAM Security File has been set up, per the 'Installation Guide', you can share between TSSMVS r14.0 and TSSMVS r15.0
To conlude, TSSMVS r15.0 requires the VSAM Security File Extension be used with the regular (BDAM) Security File. If you currently use the VSAM Security File Extension with TSSMVS r14.0, then you're good to share with TSSMVS r15.0. If you don't currently use the VSAM Security File Extension, then you can use
TSSMVS r14.0 or TSSMVS r15.0 to set it up and start sharing. Please see all of the above on the process for doing this.
Environment
Component:
Feedback
