Defining Layout Parameters for Dynamically Built More Detail Views

All types of more detail views can be dynamically built. You can specify the layout of more detail views even though you do not explicitly define the more detail views. More detail views are created when an NetView® management console operator chooses More Detail from a context menu. GMFHS attempts to build the following more detail views for objects defined in RODM:

The more detail logical view contains all of the objects specified by the ComposedOfLogical field of the selected object.
The more detail physical view contains all of the objects specified by the ComposedOfPhysical field of the selected object.
The configuration children II view contains all of the objects specified by the RelFieldNamesA field of the View_Information_Object_Class object for the configuration children II view.
The configuration children III view contains all of the objects specified by the RelFieldNamesA field of the View_Information_Object_Class object for the configuration children III view.

If the value of the ComposedOfLogical field or the ComposedOfPhysical field is null, the corresponding view is not built. Refer to Understanding Views in the IBM Z® NetView User's Guide: NetView Management Console for information about displaying more detail views.

You can specify layout parameters for each of the more detail views created from a selected object. Complete the following steps to specify layout parameters for more detail views. Figure 1 shows the objects ( A , B , and C ) and links ( 1 and 2 ) you create.

Select the object for which you want to define more-detail-view layout parameters. You are defining layout parameters for the more detail views created when this object is selected in another view.
For this example, select the aggregate object TRLAN ( A ) in the sample network.
Choose the more detail view for which you are defining layout parameters: more detail logical or more detail physical.
The TRLAN object has valid values for both ComposedOfLogical and ComposedOfPhysical, so two more detail views are created. For this example, choose to define layout parameters for the more detail physical view.
Create an object of the Layout_Parameters_For_View_Class to represent the view.
Hint: Layout_Parameters_For_View_Class objects are similar to Network_View_Class objects.
The following is part of the RODM load function statement that creates the object ( B ) for this example. The sample member DUIFSNET contains the complete statements.
```
CREATE INVOKER  ::= 0000004;
       OBJCLASS ::= Layout_Parameters_For_View_Class;
       OBJINST  ::= MyName = (CHARVAR)
                  'View_Layout_Parms_For_TRLAN_More_Detail_Physical';  
```
Link the SelectedResource field of the object you created in Step 3 to the DetailViewLayoutForSelectedResource field of the object you selected in Step 1.
The following is part of the RODM load function statement that creates this link, shown as 1 in Figure 1:
```
SelectedResource ::= (OBJECTLINKLIST) ('GMFHS_Aggregate_Objects_Class'.
'TRLAN'.'DetailViewLayoutForSelectedResource'),  
```
Specify which more detail view type this Layout_Parameters_For_View_Class object ( B ) represents. You specify the view type by linking the ViewClass field of this object to the DetailViewLayout field of an object ( C ) in the View_Information_Reference_Class that represents the view type:
- More_Detail_Logical_View_Reference
- More_Detail_Physical_View_Reference
- Configuration_Children_II_View_Reference
- Configuration_Children_III_View_Reference
The following is part of the RODM load function statement that creates the link specifying a more detail physical view, shown as 2 in Figure 1:
```
ViewClass ::= (OBJECTLINKLIST) ('View_Information_Reference_Class'.
'More_Detail_Physical_View_Reference'.'DetailViewLayout'),  
```
Specify the layout parameters for the view you are defining. The remaining fields of the Layout_Parameters_For_View_Class object ( B ) specify the layout algorithm and other view parameters. Table 1 lists the required parameters for each layout algorithm.
For this example, choose radial layout for token ring networks as the layout algorithm. Table 1 shows that the FirstNode field and SecondNode field are required for this layout. The following is part of the RODM load function statement that specifies the layout algorithm and the FirstNode and SecondNode fields:
```
LayoutType ::= (INTEGER) 4,
FirstNode  ::= (OBJECTLINK) ('GMFHS_Managed_Real_Objects_Class'.
     'LANMGR.10005AC35CA0'.'IsFirstNode'),
SecondNode ::= (OBJECTLINK) ('GMFHS_Managed_Real_Objects_Class'.
     'LANMGR.10005A95E7CC'.'IsSecondNode');  
```
If you want to use this same Layout_Parameters_For_View_Class object for additional objects or views, create additional links. All of the link fields accept multiple values.
If you need to control the layout of individual objects in the more detail view, define layout parameters for the objects. Some layout algorithms require layout parameters for the objects: Table 1 lists required parameters.
See Adding Layout Parameters for Objects in More Detail Views for instructions on defining layout parameters.

This figure shows defining layout parameters for detailed views. — Figure 1. Defining Layout Parameters for More Detail Views