SDFTREE

Purpose

SDFTREE dynamically loads an SDF tree structure definition member from the NetView DSIPARM data set or deletes a tree member from system memory.

SDFTREE can be issued from a console.

Parameters

tree_member

The name of the member containing the tree structure to load.

root_component_name

The name of the root component, which is the name that is used for level 1 in the tree structure that you want to delete. While you add a tree structure definition members by specifying a tree member name, you delete tree structure definition members by specifying a root component name.

Add

Specifies that you want to add the specified tree structure definition member.

DISKonly

Specifies that you want to add the specified tree structure member. However, any member previously loaded into storage is ignored

DELete

Specifies that you want to delete a tree structure definition member.

Restrictions and Limitations

Tree structure definition members dynamically loaded by the SDFTREE command are not reloaded when SDF is restarted. Only members that are specified in the AAO globals AOF_AAO_SDFROOT.* are reloaded. A root name that does not define the name of a tree structure member receives the default name AOFTREE. You must either add the tree definitions to AOFTREE (using %INCLUDE statements) before SDF is restarted, or manually reload them using the SDFTREE command after SDF is restarted.

Members AOFTREE and ISQTREE cannot be added using this command.

When you define a tree like the one that is supplied by System Automation in the sample member INGTCFG, you have to define the component names that belong to only the local target system in the AAO globals AOF_SDF_SDFTGT_COMP.*. The .0 variable defines the number of adjacent globals.

You need to do this for each target system individually even for the backup focal point system. For convenience, the trailing wild character asterisk (*) is supported on the component name, the alternate component name, and the major component name, but not on the root component name. For example, specification "ROOT.H*(IPL*)" matches all component names beginning with "H" and its alternate component names beginning with "IPL". In addition, system symbols are supported as well.

Normally, the RESYNC FP command deletes and refreshes on the focal point system the tree information of all root names that are found on the target system except those that are owned by System Automation like INGCFG. The component names that are defined in the globals above cause System Automation to delete and refresh only the information of the components rather than of the root names the components belong to.

On the primary focal point system, the SDF backup focal point system behaves like a normal target system. However, the backup focal point system must have the same root names defined as the primary focal point system in case the primary focal point system becomes inactive. Since SDF has been enabled to refresh the user data on the focal point as well, you need to define the static root names of the BACKUP focal point in the AAO globals AOF_AAO_SDFBFP_ROOT.n. Otherwise, the command RESYNC FP will neither delete nor refresh the information of the static root names on the primary focal point system. This is also true when the backup focal point system becomes active after the primary focal point system. The .0 variable defines the number of adjacent globals. Any adjacent global defines one or more static root names of the BACKUP focal point separated by a blank character.

Usage

• When a new tree structure is loaded to replace an existing tree structure, the status descriptors of any status component with identical names in both trees are copied to the new tree.
• When an error is detected while this command is processing, no action is taken to change the existing tree structure.