Writer instructions
Purpose	Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch. You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner. If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space. For more information, see Space-announcements-banners.
Removing	When an announcement is no longer needed, remove the BMC Space Banner macro.
Translation	Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n. See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces.
Usage	Choose one or none of the following BMC Space Banner macros. If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors. When should I use a space announcement banner? Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model. Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version. When an announcement is no longer needed, remove the BMC Space Banner macro.

Catalog and subsystem access

Displaying catalog objects is the action you’ll perform the most often when using File-AID for Db2 Object Administration. Because you’re using an object-action interface, you must always first display the objects with which you want to work.

The most frequently used methods to display objects are the following:

Catalog display facilities
Primary and row commands

Each method is discussed in this section as well as how to locate objects in other subsystems, catalogs, and locations. Once catalog objects are displayed, you can perform Db2 or File-AID for Db2 Object Administration functions such as creating or modifying.

Catalog display facilities

File-AID for Db2 Object Administration catalog display facilities quickly locate catalog objects and open a window listing the objects and selected data. The display facilities always acquire information from the current subsystem and location. Display facilities are available for each Db2 catalog object and can be selected from the Main Menu.

The display facilities have filtering criteria from which you can select. Some of these criteria build a WHERE clause for you to edit and execute. Each catalog display facility is described in Main Menu Selections. More information about filters is in Filtering Selections.

Accessing catalog display facilities with smart link

Catalog display facilities are also accessible through Smart Link. Smart Link is a Help Facility feature that locates object names when you are completing fields in a parameter window.

When you press <Help> on a field that requires an object name from the catalog, File-AID for Db2 Object Administration invokes Smart Link automatically. Smart Link pops up the appropriate catalog display facility. This facility is the same one you can access from the Main Menu. For example, if your parameter window field needs a database name, Smart Link pops up the Database Display Facility.

Use the catalog display facility’s filters to locate and display the object you need for your current operation. Then place the cursor on the object name and press Enter. File-AID for Db2 Object Administration places the name in the field and removes the catalog display facility windows.

Commands for displaying objects

Each object display has a set of commands that locate related or dependent objects. For example, a tablespace display has a command that displays dependent tables.

These commands are called navigation commands. To find out the valid navigation commands for any object display, use the Help Facility. In the row command Help window, look for the Navigate category.

File-AID for Db2 Object Administration always displays objects from the current Db2 subsystem, which is part of your session user profile. See Connecting to Db2 Subsystems for information about choosing a subsystem.

Connecting to Db2 subsystems

When accessing File-AID for Db2 Object Administration, you are connected to your current File-AID for Db2 subsystem which is then used for displaying catalog objects, as described in Catalog Display Facilities.

If you want to use Object Administration functions against objects on other Db2 subsystems defined in Db2 configuration, there are 3 ways:

Exit out of Object Administration and change the subsystem ID in the Db2 SSID field on the File-AID for Db2 Primary Option Menu or in the SSID field on the Utility Selection Menu. Then return to Object Administration.
Use either the CONNECT or LOCATION command with location-id to access remote Db2 subsystems defined in your Db2 configuration. See DSN-Change-View-Profile for more information. See CONNECT-Connect-to-Server and LOCATION-Specify-Remote-Location for more information.
Use DSN command to dynamically switch the current Db2 subsystem connection and allocated Db2 data sets. For more information, see File-AID for DB2 — Object Administration Setup for DSN Command in the Configuring BMC Compuware File-AID for Db2for one time activation procedure.

When selecting another subsystem with the DSN primary command, you select the appropriate view profile. The name of the view profile can be specified as a parameter to the DSN command. Or, you can execute DSN in any window without a parameter to open a window listing all view profiles available to you. See DSN-Change-View-Profile for more information.

View Profiles and Your Session

View profiles are created during the File-AID for Db2 installation process. A profile contains a subsystem’s characteristics such as the catalog and plan name.

The following summary describes how a view profile affects your File-AID for Db2 Object Administration session:

Each Db2 subsystem is a view profile.
View profiles may reference different Db2 release levels; see Multiple Db2 Releases.

Once a new subsystem is selected, subsequent windows in that navigation path contain data from your selected subsystem. The current view profile is part of your session user profile.

Important

When the CONNECT primary command is issued to access another subsystem, the values in your current view profile will be used in the subsystem to which you are connecting.

For more information on the CONNECT primary command, see CONNECT-Connect-to-Server.

Multiple Db2 Releases

File-AID for Db2 Object Administration supports concurrent access of multiple releases of Db2.

To access another release of Db2, use the DSN primary command (see DSN-Change-View-Profile). In the view profile selection list that pops up, the profile descriptions should indicate the Db2 release level. If not, place the cursor on the text description and press Enter to open a window indicating the Db2 release and other system parameters. Once a new profile is selected, subsequent windows in that navigation path will contain data from your selected subsystem.

The following figures show examples of table displays for table EMP created in different Db2 versions.

Table Editing Windows for a Db2 Version 9 subsystem

Table Editing Windows for a Db2 Version 10 subsystem

Distributed database support

You can use File-AID for Db2 Object Administration to access Db2 subsystems at remote locations. Use either or both of the following Db2 access methods:

System-directed access
Application-directed access

Specifying System-Directed Access

To specify a location for system-directed access, use the LOCATION primary command (see LOCATION-Specify-Remote-Location). If you execute LOCATION without a parameter, File-AID for Db2 Object Administration opens a window listing locations from which you can select. Also, if you know the name of the location, you can specify it as a parameter to the LOCATION command.

Once you specify a location, File-AID for Db2 Object Administration generates a three-part name for objects that lets Db2 determine where a query is to execute. To return to local mode, specify LOCATION RESET.

The name of the location, if specified, appears in the bottom border of the windows with the LOC.

System-Directed Access. Only the bottom portion of the window is shown.

Specifying Application-Directed Access

To specify application-directed access, use the CONNECT primary command; see CONNECT-Connect-to-Server. This allows an explicit connection to any REMOTE server. File-AID for Db2 Object Administration’s CONNECT command generates the necessary Db2 CONNECT statement.

Executing CONNECT without a parameter pops up a list of valid locations from which you can select. Also, if you know the name of the location, you specify it as a parameter to the CONNECT command. To return to local mode, execute CONNECT RESET.

If you set a remote location with the CONNECT command, the name of the location appears in the bottom border of the windows with the CON prefix (see the following figure).

Application-Directed Access. Only the bottom portion of the window is shown.

Using Remote Locations

The following guidelines apply to both system-directed and application-directed access.

All work buffers except the SQL work buffer are local mode only. Other windows may be local mode only as indicated in the bottom border of the window. For information about executing SQL work buffer contents at remote locations, see Submitting or Executing Work Buffer Contents.
Once a remote location is set (through the CONNECT command or the LOCATION command), all subsequent windows use the remote location. See Scope of LOCATION and CONNECT Commands.
You can specify either system-directed access or application-directed access. Activating one automatically deactivates the other.
Valid locations are defined to File-AID for Db2 Object Administration during installation.

Command Validity at Remote Locations

Not all commands are valid at remote locations. To find out about a specific command, open the row command Help window. The Mode column, which displays when a remote location is set, indicates if the command is valid (see the following figure). NOLOC indicates the command cannot be executed through system-directed access. NOCON indicates the command cannot be executed through application-directed access.

If the location is set to local, the Mode column does not show in the Help window.

Help Window for Row Commands with Remote Location Set. The Mode column indicates remote location restrictions

Scope of LOCATION and CONNECT Commands

Once a remote location is specified, all subsequent windows will use the new location. This is unlike the DSN command, which affects only the current navigation path.

This may lead to a situation where you have objects displayed from one location, but the current location is different. For example, you might generate a table object display from one location, and then change the location. The table object display still shows the objects from the first location. If you execute a row command on that table display, however, that command will execute using the new location. The window that opens will display objects from the new location.