AKDINI configuration values

The AKDINI member (the product initialization member) of the SAKDPARM library is used to define global information regarding Advanced Audit for DFSMShsm usage and options.

The AKDINI member is organized in sections. A section name is indicated by the colon character (:), immediately followed by the section name (:PRODUCT_INFO, for example). Do not change or add section names except under direction from Technical Support.

Each section contains a set of individual parameter specifications known as token statements. The general format for a token statement is:

Token = Value

Tokens are set with a value, specified by you or the Support Center, that is a set of strings to the right of the token's equal (=) sign. Token values may be keywords, user values, or a keyword with a user value, shown as VALUE(uservalue).

You can enclose values in either single (') or double (") quotes. The quotes are stripped away before the product uses the value. Quotes may be supplied as data by either of these methods:

Using the opposite quote symbol as delimiters (for example, " ' " yields a single quote as data).
Specifying two to get one (for example, ' ' ' yields a single quote as data).

Leading blanks from the beginning of the logical card-image records are allowed for all token statements. Syntax scan processing locates the first nonblank character in each logical record. The entire length of the 80-byte logical record is considered for valid data. Do not renumber the AKDINI member sequence numbers assigned in columns 73 through 80 because this will cause errors to occur.

Continuing a token statement

Token statements can be continued, using either a minus (-) or plus (+) character anywhere within the text. All data to the right of the continuation character on that logical record are interpreted as a comment and ignored.

Reading the token statements

The token statements shown in this document follow these rules:

Default values are underlined.
Multiple values are separated with a vertical bar ( | ). You must choose one.
User-supplied values are in lowercase italic. For example, text.

Commenting Rules

Both line mode and block mode methods of commenting are supported:

An asterisk (*) in column 1 marks the entire line as a comment. This style of comment is not allowed inside a continued /* */ type comment, but is allowed in a continued token/value statement.
Entire lines, blocks of lines, or portions of a line may be commented by beginning the comment with a forward slash and an asterisk (/*) and terminating the comment with an asterisk and a forward slash (*/). Nested comments are honored.

You can add a Notes token to document changes to any section including the initial or unnamed section. The AKDINIMG program retains these notes along with any comments that continue from the Notes token. For example:

Notes  = /* Updated by Dan
            on 2016/05/01  */

You can also use a portion of the section-statement line after the first space for documenting changes to that section. For a multi-image INI, the section name can be qualified by sysplex, system name, or both as shown below, except for the PRODUCT_INFO section:

Sysplex-name and system-name qualification:
```
:section-name.sysplex-name.system-name
```
Sysplex-name only qualification:
```
:section-name.sysplex-name
```
System-name only qualification:
```
:section-name..system-name 
```

The sysplex and system names must be explicitly specified with no wildcard characters allowed.

Those programs using the AKDINI use only the first matching section. All other variations of that section are ignored. You can specify qualified sections for those images with unique requirements, followed by an unqualified section that applies to all of the other images.