Migrating from SYSVIEW 15.0 to 16.0 and using the default installation provided security file, SYS1.SYSVIEWE.CNM4BSEC, the dataset name will be the same on 16.0.
Applying SYSVIEW 16.0 installation to a separate set of disks, and it will be made effective with an IPL.
Taking the JCL for INST0050 from SAMPJCL and tailoring it to the system, but as the security file has the same name, will the convert utility handle it accordingly ?
Is something like the JCL below adequate to perform the conversion ?
//CNVTSECU EXEC PGM=GSVXCNVS,PARM='GSVX'
//STEPLIB DD DISP=SHR,DSN=SYS1.SYSVIEWE.CNM4BLOD
//*
//GSVXSCFG DD DISP=SHR,DSN=SYS1.SYSVIEWE.CNM4SCFG
//*
//SYSUT1 DD DISP=SHR,DSN=SYS1.SYSVIEWE.CNM4BSEC,
// UNIT=SYSDA,VOL=SER=MGXS21 <=== Previous Disk for V15 file
//SYSUT2 DD DISP=SHR,DSN=SYS1.SYSVIEWE.CNM4BSEC,
// UNIT=SYSDA,VOL=SER=MGXS11 <== Current Disk for V16 File
//*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
FAILNEWCMDS=YES,GROUP=*ALL*
FAILNEWCMDS=NO,GROUP=ADMIN
SYSVIEW 15.0 & 16.0 - z/OS supported releases -
1. Create the new SYSVIEW 16.0 security file: SYS1.SYSVW160.CNM4BSEC with the INST0001 job on volume A and uncatalog it.
2. Create a new SYS1.SYSVW160.CNM4BSEC from SYS1.SYSVW150.CNM4BSEC (15.0 sysview security file) and copy SYS1.SYSVW150.CNM4BSEC in SYS1.SYSVW160.CNM4BSEC (volume B) for the sysut1 dd in step CNVTSECU in the INST0050 job.
3. Uncatalog SYS1.SYSVW160.CNM4BSEC (volume B) which is the old 15.0 sysview security file and put it in sysut1 in step CNVTSECU in the INST0050 job (volume B).
4. Catalog SYS1.SYSVW160.CNM4BSEC on volume A and put it in sysut2.
Run the INST0050 job, step CNVTSECU, the result is correct:
CA SYSVIEW 16.0 0990 Security Conversion Utility
Input: SYSUT1 SYS1.SYSVW160.CNM4BSEC volume B
Output: SYSUT2 SYS1.SYSVW160.CNM4BSEC volume A
Converted group GLOBAL
Converted group DEFAULT
Converted group ADMIN
Converted group NOACCESS
Converted group SACHAR