Explanation of the example directory definition file

The directory definition file contains comments and directory entries:
  • Comments are not processed. They begin with the # symbol in column 1. Blank lines are treated as comments.
  • Directory entries determine which associations are allowed, and for those associations, what type of security is to be used.

Each directory entry contains attributes and their values. An attribute is similar to a VTAM® operand, in that the attribute and the value specified on it define a characteristic of an object. In the directory definition file, the object is CMIP services.

The value is a single expression, which can contain blanks if the value is enclosed in quotation marks. Everything after the value in a directory entry record is treated as a comment record and is not processed.

An entry ends where the next entry begins (with a different name or class attribute) or at the end of the directory definition file.

The first attribute in the example directory definition file is the class attribute, with the value aetitle. See Format of directory definition file entry records for an explanation of class. This entry specifies that the names under the class attribute are assumed to be CMIP services names or names of CMIP application programs that have registered their own AE titles. For a description of AE titles, see z/OS Communications Server: CMIP Services and Topology Agent Guide.

The class and its attribute are followed by the second attribute, name with a value. The required name attribute is the first attribute for an object that belongs in the class specified by the preceding class attribute. CMIP services searches for the name attribute in the directory definition file when it determines whether a particular instance of CMIP services can have an association with CMIP services on this host.

The third attribute is the associationKey attribute with a value. Specifying associations is discussed in the following information.