Steps to create the installation options data set

The installation options data set is a file that you create that contains installation options. It becomes active when you start ICSF.
  • The installation options data set can be a member of PARMLIB, a member of a partitioned data set, or a sequential data set.
  • The format of each record in the data set must be fixed length or fixed block length.
  • A physical line in the data set is 80 characters long. The system ignores any characters in positions 72 to 80 of the line.
  • A logical line is one or more physical lines. You can group physical lines into a logical line by placing a comma at the end of the information. Only a comment can appear after the comma. The system ignores any other information between the comma and column 71.
  • Continuation causes the next physical line to append immediately following the comma. The system removes all leading blanks on the next physical line.
  • You can delimit comments by /* and */ and include them anywhere within the text. A comment cannot span physical records. The system removes comments from a logical line before parsing it. It ignores physical lines that contain only comments.
  • Specify only one option setting or keyword on a logical line. (If you specify more than one, the system ignores all but the last one on the line. The system reports syntax errors, but the errors do not cause it to stop interpreting the file.)

ICSF provides a sample installation options data set. The sample data set uses the recommended values for each option.

  1. When you are starting ICSF for the first time:
    1. Change the name of the data set on the CKDSN and PKDSN statements to the name of the empty VSAM datasets you created previously (in Step 3 and Step 4).
    2. For a complete description of options you may want to change after the first start, see Customizing ICSF after the first start.)
  2. Store the updated data set in SYS1.PARMLIB.
    Note: For convenience, the installation options data set generally resides in SYS1.PARMLIB. If your cryptographic administrator does not have update access to SYS1.PARMLIB, store installation options in another data set, and RACF-protect it.
The sample installation options data set is as follows in SYS1.SAMPLIB: CSFPRM00 
/*******************************************************************/           
/*     LICENSED MATERIALS - PROPERTY OF IBM                        */           
/*                                                                 */           
/*     5650-ZOS                                                    */           
/*                                                                 */           
/*     COPYRIGHT IBM CORP. 1990, 2013                              */           
/*                                                                 */           
/*  THIS IS A SAMPLE OF THE ICSF OPTIONS DATASET                   */           
/*                                                                 */           
/*******************************************************************/           
CKDSN(CSF.CSFCKDS)                                                              
PKDSN(CSF.CSFPKDS)                                                              
COMPAT(NO)                                                                      
SSM(NO)                                                                         
CHECKAUTH(NO)                                                                   
CTRACE(CTICSF00)                                                                
USERPARM(USERPARM)                                                              
REASONCODES(ICSF)
Note: See Parameters in the installation options data set for descriptions of these parameters.

Use of system symbols in the options data set is supported. System symbols can be used as values for any of the parameters. System symbols must be no more than 8 characters.

Note: ICSF allows the CKDS, PKDS and TKDS data set names to be a maximum of 44 characters with up to 21 qualifiers. Also, the first character must be alphabetic.

See Parameters in the installation options data set for additional information.

This example shows how system symbols could be used for the CKDS and PKDS data set names. You could use a SYS1.PARMLIB(IEASYMxx) file and modify CSFPRM00.

IEASYMxx file could contain: 
/*------------------------------------*/
/* SYSTEM SYMBOLS FOR ICSF CRYPTO     */
/*------------------------------------*/
SYSDEF
 SYMDEF(&CKDSN001='CSF')
 SYMDEF(&CKDSN002='CSFCKDS')
 SYMDEF(&PKDSN001='CSF')
 SYMDEF(&PKDSN002='CSFPKDS')
CSFPRM00 could be modified as follows.
/*******************************************************************/  
/*     LICENSED MATERIALS - PROPERTY OF IBM                        */  
/*                                                                 */  
/*     5650-ZOS                                                    */  
/*                                                                 */  
/*     COPYRIGHT IBM CORP. 1990, 2013                              */  
/*                                                                 */  
/*  THIS IS A SAMPLE OF THE ICSF OPTIONS DATASET                   */  
/*                                                                 */  
/*******************************************************************/  
CKDSN(&CKDSN001..&CKDSN002)                                                              
PKDSN(&PKDSN001..&PKDSN002)                                                              
COMPAT(NO)                                                                      
SSM(NO)                                                                         
CHECKAUTH(NO)                                                                   
CTRACE(CTICSF00)                                                                
USERPARM(USERPARM)                                                              
REASONCODES(ICSF)
This example shows how system symbols could be used for the Regional Cryptographic Server (RCS) port numbers. You could use a SYS1.PARMLIB(IEASYMxx) file and modify CSFPRM00.
IEASYMxx file could contain:
/*------------------------------------*/
/* SYSTEM SYMBOLS FOR ICSF CRYPTO     */
/*------------------------------------*/
SYSDEF
SYMDEF(&RDPORT='1125')

CSFPRM00 could be modified as follows.

/*******************************************************************/
/* LICENSED MATERIALS - PROPERTY OF IBM                            */
/*                                                                 */
/* 5650-ZOS                                                        */
/*                                                                 */
/* COPYRIGHT IBM CORP. 2015                                        */
/*                                                                 */
/* THIS IS A SAMPLE OF THE ICSF OPTIONS DATASET                    */
/*                                                                 */
/*******************************************************************/
CKDSN(CSF.CSFCKDS)
PKDSN(CSF.CSFPKDS)
TKDSN(CSF.CSFTKDS)
COMPAT(NO)
SSM(NO)
CHECKAUTH(NO)
CTRACE(CTICSF00)
USERPARM(USERPARM)
REASONCODES(ICSF)
REMOTEDEVICE(1,MY.SERVER.DOMAIN.COM,&RDPORT,8)

When the machine or partition is IPLed, specify within the load parameter the
symbol file that should be used. For example, if the previous symbol file was
called IEASYM01, then within the load member, the IEASYM entry might look like
IEASYM(00,01); where 00 denotes the IEASYM00 file (usually the system default)
and 01 denotes the IEASYM01 file.

When the machine or partition is IPLed, specify within the load parameter the symbol file that should be used. For example, if the previous symbol file was called IEASYM01, then within the load member, the IEASYM entry might look like IEASYM(00,01); where 00 denotes the IEASYM00 file (usually the system default) and 01 denotes the IEASYM01 file.