Migrating an ADCD z/OS release to the next release: ICSF

Start here:Migrating an ADCD z/OS release to the next release.

Depending on your setup, migrating ICSF to a newer level can be trivial.

With my original ADCD system, it had ICSF set up to use data sets like CSF.CSFCKDS. When I moved to a new level of ADCD, there were the same data set names.

I backed up the datasets, and restored them on the new system with a new name

//IBMDFDSS JOB 1,MSGCLASS=H 
//  SET BACKUP=COLIN.CSF.Z24C.BACKUP 
//SDE EXEC PGM=IEFBR14,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,DELETE), 
//         SPACE=(CYL,(1,1)) 
//S1  EXEC PGM=ADRDSSU,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,CATLG), 
//         SPACE=(CYL,(50,50),RLSE) 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * 
 DUMP  - 
    DATASET(INCLUDE(CSF.SCSFCKDS,        - 
                    CSF.SCSFPKDS,    - 
                    CSF.SCSFTKDS  )- 
           )    - 
    OUTDDNAME(TARGET) - 
    COMPRESS 
/* 

I restored them on the same system using

//IBMDFDSS JOB 1,MSGCLASS=H                           
//S1  EXEC PGM=ADRDSSU,REGION=0M PARM='TYPRUN=NORUN'  
//TARGET   DD DISP=SHR,DSN=COLIN.CSF.Z24C.BACKUP      
//SYSPRINT DD SYSOUT=*                                
//SYSIN DD *                                          
 RESTORE -                                            
    DATASET(INCLUDE(**)      )                   -    
    RENAME(COLIN ) -                                  
    INDDNAME(TARGET)                                  
/*                                                    

I now had data sets like COLIN.SCSFPKDS.

Remember to change your backup processes to backup the new data sets.

The default CSF procedure is

//CSF PROC 
//CSF EXEC PGM=CSFINIT,REGION=0M,TIME=1440,MEMLIMIT=NOLIMIT 
//CSFPARM DD DSN=ADCD.&SYSVER..PARMLIB(CSFPRM00),DISP=SHR 

Which does not easily allow you to override it. In USER…PROCLIB(CSF) I created

//CSF  PROC PRM=CP 
//CSF  EXEC PGM=CSFINIT,PARM=&PRM,REGION=0M,TIME=1440,MEMLIMIT=NOLIMIT 

and in USER….PARMLIB(CSFPRMCP) created

CKDSN(COLIN.SCSFCKDS) 
PKDSN(COLIN.SCSFPKDS) 
TKDSN(COLIN.SCSFTKDS) 
DOMAIN(0) 
COMPAT(NO) 
SSM(NO) 
CHECKAUTH(NO) 
CTRACE(CTICSF00) 
USERPARM(USERPARM) 
REASONCODES(ICSF) f

Compared to the ADCD provided member, my member has

• Different dataset names
• A TKDSN dataset
• DOMAIN(0)

Creating a TKDS

As part of my use of ICSF tokens for certificates I had to create a TKDS.

I used Steps to create the TKDS, using data set name COLIN.SCSFTKDS.

Don’t forget to add it to your list of data sets to backup regularly.

Starting ICSF

With the ADCD system you start ICSF using the operator command S CSF or S CSF,PRM=xx .

From ISPF go to option 6 TSO and use the @ICSF command