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 two sample installation options data sets. These
sample data sets use the recommended values for each option.
- When you are starting ICSF for the first time:
- 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).
- Change SSM(NO) to SSM(YES).
- For a complete description of options you may want to change after
the first start, see Customizing ICSF after the first start.)
- 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 two sample installation options data sets are as follows in
SYS1.SAMPLIB:
- CSFPRM00
/*******************************************************************/
/* LICENSED MATERIALS - PROPERTY OF IBM */
/* */
/* 5694-A01 */
/* */
/* COPYRIGHT IBM CORP. 1990, 2008 */
/* */
/* THIS IS A SAMPLE OF THE ICSF OPTIONS DATASET */
/* */
/*******************************************************************/
CKDSN(CSF.CSFCKDS)
PKDSN(CSF.CSFPKDS)
COMPAT(NO)
SSM(NO)
KEYAUTH(NO)
CKTAUTH(NO)
CHECKAUTH(NO)
TRACEENTRY(10000)
USERPARM(USERPARM)
REASONCODES(ICSF)
- CSFPRM01 (batch setup for SMP/E)
/*******************************************************************/
/* LICENSED MATERIALS - PROPERTY OF IBM */
/* */
/* 5694-A01 */
/* */
/* COPYRIGHT IBM CORP. 1990, 2008 */
/* */
/* THIS IS A SAMPLE OF THE ICSF OPTIONS DATASET */
/* */
/*******************************************************************/
CKDSN(CSF.CSFCKDS)
PKDSN(CSF.CSFPKDS)
COMPAT(NO)
SSM(YES)
KEYAUTH(NO)
CKTAUTH(NO)
CHECKAUTH(NO)
TRACEENTRY(10000)
USERPARM(USERPARM)
REASONCODES(ICSF)
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. ICSF allows the CKDS and PKDS data
set names to be a maximum of 44 characters with up to 21 qualifiers.
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 CSFPRM01.
IEASYMxx file could contain:
/*------------------------------------*/
/* SYSTEM SYMBOLS FOR ICSF CRYPTO */
/*------------------------------------*/
SYSDEF
SYMDEF(&CKDSN001='CSF')
SYMDEF(&CKDSN002='CSFCKDS')
SYMDEF(&PKDSN001='CSF')
SYMDEF(&PKDSN002='CSFPKDS')
CSFPRM01 could be modified as follows:
/* */
/* LICENSED MATERIALS - PROPERTY OF IBM */
/* */
/* "RESTRICTED MATERIALS OF IBM" */
/* 5694-A01 */
/* */
/* (C) COPYRIGHT IBM CORP. 1990, 2008 */
/* */
/* */
CKDSN(&CKDSN001..&CKDSN002)
PKDSN(&PKDSN001..&PKDSN002)
COMPAT(NO)
SSM(YES)
KEYAUTH(NO)
CKTAUTH(NO)
CHECKAUTH(NO)
TRACEENTRY(10000)
USERPARM(USERPARM)
REASONCODES(ICSF)
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.
For SMP/E, CSFPRM01 can be copied to the CPAC.PARMLIB data set.
The CKDS and PKDS data set names in CSFPRM01 need to match in Server-Pac.
Outside of Server-Pac, you need to copy and edit CSFPRM01.
|