Using Customization Tables and Methods

You might need to customize the mapping of OSI status to display status, the resolved status for resources created in RODM, and the resources in exception views. This information is stored in customization tables that you can copy, change, use, and extend. The tables are stored as members in the appropriate DSIPARM data set:

• FLBOSIDS, the OSI-display status table
• FLBSRT, the status resolution table
• FLBEXV, the exception view table

You can also use object-independent methods to perform customization.

The tables are read at initialization and re-read whenever you issue a TOPOSNA REFRESH command for one or more of the tables. If a class is missing when the table is read, warning message FLB666W is issued, but processing continues. If you receive that message, correct the table and issue another TOPOSNA REFRESH command to refresh the table.

These status tables and methods are used by the SNA topology manager for all status updates except for those objects whose DisplayStatus is set to unknown during SNA topology manager warm-start processing. During warm start, the SNA topology manager changes each DisplayStatus to unknown for all real objects managed by the SNA topology manager (with a ResourceTraits field value of RESET) that remain in RODM after purging the applicable objects. When a field changes to the default value during warm start, no methods installed on this field are run. See Planning for Warm Starts for additional information.

You must specify the class defaults first, then specify any changes for specific resources. All entries for one class can be specified together, followed by entries for the next class, and the next class until all specifications are complete. If you need to customize values only for specific resources, do not replace the existing tables. Instead, make entries in the sample file specified by the %INCLUDE card at the end of each default table (listed in Table 8). The three customization tables support the use of the %INCLUDE card, which is described in the IBM Tivoli NetView for z/OS Administration Reference. In the file named by the %INCLUDE, list the class, the specific resource names whose values you want to customize, and the new values. The descriptions and examples in this chapter provide more details. For convenience, each of the default files has an %INCLUDE card that names a sample file that is empty. Symbolic names can be used. For example, APPLPASS="&DOMAINNV" is valid.

[ Top of Page | Previous Page | Next Page | Contents ]