This site will undergo a maintenance outage on Saturday, 13 September beginning at 2:30 AM Central/1 PM IST for a platform upgrade. The downtime will be ~three hours.

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.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Step 8— Specifying extract scope


After selecting option 2 from the Extract Menu File-AID/RDX displays the Extract Scope screen shown in the following figure. Your current profile prefills the fields on this panel. Verify that the values match.

File-AID/RDX ------------------ Extract Scope ---------------------------------
Command ===>                                                    

Driving Object: DSNLOCAT.FRSAMP.ORDER_TABLE                                     
                                                                               
Extract Navigation Criteria:                                                    
  Direct    ===> Y               ( Y = Yes, N = No)                             
  Parents   ===> Y                                                              
  Siblings  ===> N                                                              
  Indirect  ===> Y                                                              
  Extract scope detail view ===> O   ( O = Object, R = Relationship, N = None)  
Extract Options:                                                                
  Cycle count                                 ===> *        ( * for no maximum)
  Maximum total rows/records from all objects ===> 50       ( * for no maximum)
  Action when maximum count is reached        ===> Q   ( Q = Quiesce, S = Stop)
  Extract from DB2 using Uncommitted Reads    ===> Y        ( Y = Yes,  N = No)
  Extract IMPLICITLY HIDDEN columns           ===> N        ( Y = Yes,  N = No)
  Extract from image copy                     ===> N        ( Y = Yes,  N = No)
  SELECT FROM Temporal Table                  ===> N                      *None*
Scope Summary Counts:                                                           
  12 of  12 Relationships Active
    Related DB2 objects..:   6 of   6 included                                      
    Related MVS objects..:   6 of   6 included                                      
    Output Key Files.....:   0 of   0 included


Verify extract options as set with User profile SAMPMENU:

In this field…

Do the following:

Extract Navigation Criteria

Set the global navigation controls to:

Direct ===> Y
 Parents ===> Y
 
Siblings ===> N
 
Indirect ===> Y

Extract Scope Detail View

Type O for File-AID/RDX to display the listing of the related objects.

Cycle Count

This field has been locked by the current profile’s setting (see Maximum cycles).

Maximum Total Rows/Records From All Objects

Type 50 limit the extract to 50 extracted records.

Action When Maximum Count Is Reached

Type Q for File-AID/RDX to resolve all orphan records after maximum count has been reached.

Extract from DB2 using Uncommitted Reads

Type Y.

Extract IMPLICITLY HIDDEN columns

Leave set to N.

Extract from image copy

Type N.

SELECT FROM Temporal Table

Leave set to N.

Press Enter

File-AID/RDX displays the Extract Scope - Object View screen.

Field Names and Descriptions

The following list describes all of the fields in this window.

FIELD

DESCRIPTION

Driving Object

Displays the name of the driving object from which you want to extract related data.

Extract Navigation Criteria






Navigation criteria determines the extend of how File-AID/RDX chases the related objects from the driving object. On this panel, you specify the Navigation Criteria globally, for all included objects and relationships. In the Detail View panels you may then determine the navigation on an individual object or relationship level.

Important

When your profile has navigation criteria Direct set to C or P, all Extract Navigation Criteria fields are protected and cannot be modified during the extract specification. The Description of the Direct field will then also display the respective status, either ** Children only or ** Direct Plus.

Direct

Specify to extract the dependents of the driving object (starting point) and their dependents.

Y

Extract the dependents of the driving object and their dependents.

N

Do NOT extract the dependents of the driving object and their dependents.

C

(All Children only) Extract the dependents of the driving object and all of their dependents only. This option ignores all other Navigational Criteria Options (DPSI) settings and cannot be modified during the extract specification.

Using the C method to extract data and only its dependent data can lead to extracted data that is not loadable because of referential integrity issues due to the omitted related parent data. This can be useful for extracting specific data that is then used for a purge procedure.

P

(Plus) Extract all of the direct relationships of the driving object, i.e. all of its parents and first level dependents only. Direct "Plus" means resolve all objects’ parents until there are no more parents to return. This option ignores all other Navigational Criteria Options (DPSI) setting sand cannot be modified during the extract specification.

Important

The C and P settings for Direct can only be set in the profile. The profile settings are used to build the relationship tree with its related objects when starting an extract specification.

Parents

Extract the parents of all extracted data to maintain the integrity of the extracted data.

Siblings

Extract other dependents of the extracted parents from the same relationships.

Indirect

Extract other dependents of the extracted parents from other relationships.

Extract Scope Detail View




Specify whether you want to view the list of relationships or list of related objects. Set to or O to view the related objects and their relationships in more detail. In the detail panels, you may apply extract and navigation controls to individual relationships or objects.

N (None)

None does not display either of the detail extract scope panels.

O (Object)

Object displays the Extract Scope - Object View panel, listing all objects related to the driving object from which to extract data. For more information, see Extract Scope - Object View.

R (Relationship)

Relationship displays the Extract Scope - Relationship View panel, listing all the relationships associated with the driving object from which to extract data. For more information, see Relationship Navigation Criteria.

Extract Options








Use these fields to limit the number records to be extracted in this request.

Cycle Count


Specify the maximum number of cycles for all relationships leading from the object. Cycle count limits the number of times an object can be visited during an extract. This global setting for the Cycle Count can be overridden for each individual relationship (see Cycle).

 Maximum Total Rows/Records From All Objects

Specify the maximum number of rows or records you want to extract from all related objects. Enter an asterisk (*) to set no limit.

Action When Maximum Count Is Reached

Specify how the extract should terminate when the maximum count has been reached:

Q

Quiesce resolves all orphan records after maximum count has been reached. (May result in more records than the maximum count.)

S

Stop does not resolve possible orphan records (may extract dependent records without their parents).

Extract from DB2 using Uncommitted Reads

Specify whether File-AID/RDX should extract data from Db2 objects that include Uncommitted Reads or not.

The field is prefilled with the specified UNCOMMITTED_READ_DEFAULT configuration parameter value (Yes or No) of the Db2 Environment PARMLIB member or with the current profile value (Yes or No) if UNCOMMITTED_READ_DEFAULT is set to blank (default). For more information, see UNCOMMITTED_READ_DEFAULT in the Db2 environment.

Extract IMPLICITLY HIDDEN columns

Specify whether File-AID/RDX should extract data from Db2 columns that are defined as IMPLICITLY HIDDEN. When this option is set to Y, the resulting File-AID/RDX extract file will include the data from IMPLICITLY HIDDEN columns.

Extract from image copy

Specify whether File-AID/RDX should extract data from Db2 Image Copy data sets or not. This option is only available if your site installation set the parameter variable UIMGCPY to Yes. For more information, see ALLOW_EXTRACT_FROM_DB2_IMAGE_COPY in File-AID/RDX Product Configuration.

Y

File-AID/RDX extracts related data from the most recent, full Db2 Image Copy for the applicable tablespaces.

For partitioned tablespaces, File-AID/RDX extracts related data from image copy data sets as follows:

  • If the most recent image copy is for the entire tablespace, File-AID/RDX uses entire the data set name.
  • If the most recent image copy is for a partitioned tablespace, File-AID/RDX collects the data set names from the catalog for all other partitions and uses those names.

An image copy data set must exist in the MVS catalog for each Db2 table in the extract request. If not, the extract terminates.

To extract data from a Db2 Image Copy, you must have one of the following authorization privileges:

  • RECOVERDB privilege for the database
  • DBADM, or DBCTRL authority for the database
  • SYSCTRL or SYSADM authority

N

File-AID/RDX will extract from the regular Db2 tables.

Important

The Extract from image copy option requires that File-AID/RDX be executed from an authorized library. Furthermore, the Extract from image copy option is not available:

  • for Db2 views.
  • for interactive execution (see also  MODE ).
  • when extracting from a remote location.

SELECT FROM Temporal Table

Enter Yes if you want to specify or modify a time-period and date/timestamps for Temporal Tables or Temporal Views. File-AID/RDX will display the “SELECT FROM Temporal Table” screen when you press Enter. Starting with Db2 Version 11, temporal support allows period specifications and period clauses to be specified for views. The same rules apply for views as do for tables.

Enter No (default) if you don’t want to display the “SELECT FROM Temporal Table” screen.

The status *Defined displays if a SELECT FROM Temporal Table statement has already been defined, otherwise *None* displays.

If you want to extract data from temporal tables or views without a SELECT FROM Temporal Table statement, make sure *None* displays. To change the status from *Defined to *None*, enter Yes in the SELECT FROM Temporal Table field, then set the Use System Time and Use Business Time to No in the “SELECT FROM Temporal Table” screen.

Important

  1. When the *Defined * status displays and the extract request includes one or more temporal tables or views, File-AID/RDX will include the SELECT FROM Temporal Table statement even if the SELECT FROM Temporal Table field is set to N.
    The SELECT FROM Temporal Table statement is only generated for each Temporal Table or Temporal View in the extract request.
  2. Whenever the selection is based on SYSTEM_TIME, it is possible that some rows come from the base table and some from the history table.
  3. The *Defined * status is saved for this extract.
  4. The SELECT FROM Temporal Table field will be reset to its default (No, *None*) when you exit the extract - DB2 Driving Object screen.

Scope Summary Counts





The following fields display how many objects and relationships will be included in the extract based on the specified Navigational Criteria specified.

Relationships Active

Displays how many relationships will be used to extract data from the related objects.

Related DB2 objects

Displays how many related Db2 objects will be accessed to extract data from.

Related MVS objects

Displays how many related MVS objects will be accessed to extract data from.

Output Key files

Displays for how many Output Key files File-AID/RDX will create for this extract request.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*