Configuring parameters

This section describes all the configuration parameters supported by BMC AMI Security Administrator. Many of the parameters are optional and most Security Administrator solutions use only a subset.

Configuration parameter syntax

The parameters in the configuration data set conform to the following rules:

Only one parameter is allowed on each line and can start in any position on that line.
Parameters must be specified in full and are not case sensitive except for HFS path names.
A line with an asterisk * in the first position is treated as a comment.
Security Administrator parameters support standard z/OS ampersand-prefixed- (&) variables; for example &SYSNAME.

Configuring SCOPE parameter

The parameters in the Configuration data set can optionally be shared between multiple address spaces and multiple LPARs.

Parameter SCOPE controls which parameters in the configuration data set are parsed and processed by each address space on each LPAR. A block of one or more configuration parameters can be preceded by a SCOPE keyword indicating that the block is to only be processed by the address space(s) that have that scope. The scope for each address space is defined on the SCOPE= parameter in the EXEC PARM in the JCL procedure.

The SCOPE keyword can be further qualified by the SYSID, allowing different parameter blocks to be processed depending on the system Security Administrator is being started on.

*
* Following parameters will be processed by every
* Address Space
*
Parameter Value
Parameter Value
*
* Following parameters will be processed by every
* Address Space started with Scope=Server
*
Scope Server
Parameter Value
Parameter Value
*
* Following parameters will be processed by all
* Address Spaces started with Scope=SSPR1
*
Scope SSPR1
Parameter Value
Parameter Value
*
* Following parameters will be processed by Address
* Spaces started with Scope=Server on system SYS1
*
Scope SSPR1.SYS1
Parameter Value
Parameter Value

Multiple configuration parameter members

The Security Administrator configuration parameters can be split across multiple members for simplification, ease of administration or to share commonly used blocks of parameters across multiple address spaces.

Other members may be included in the parameters using the INCLUDE keyword:

*
* racfGUI Global Parameters
*
Parameter Value
Parameter Value
*
* racfGUI Server Parameters
*
Scope Server
Include member1
Include member2

Configuration parameter groups

Except for the Global Configuration Parameters described below, Security Administrator configuration parameters are organized in groups, with a group header and group trailer parameter.
This enables similar parameter keywords, such as PORT or IPAddress, to be placed inside different groups without conflict.The typical format of a parameter group is:

GroupType
   Group Parameters
   Group Parameters
   Group Parameters
EndGroupType

Parameter groups should not be split across different configuration data set members.