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 5—Specifying Target Environment

File-AID/RDX displays the Target Environment screen illustrated in the following figure when you enter the END primary command from the Source to Target Mapping screen as Option 3 is the next selected Load Option. Review the list of MVS and Db2 objects File-AID/RDX will load in the target environment. If the objects don’t exist, File-AID/RDX will attempt to create them before loading.

Important

  1. File-AID/RDX only creates Db2 objects for which the complete DDL information has been captured in the extract file.
  2. If the extract file includes data extracted from Db2 views, File-AID/RDX will load the view data into a target view only if the view already exists. If the target view does NOT exist, File-AID/RDX will create the view as a Db2 table based on the extracted CREATE VIEW DDL, without an index.
  3. The auto-create feature of Load does not support creating Temporal Tables.
  4. The auto-create feature of Load does not support creating multi-volume data sets for any MVS data set type.

Target Environment

 File-AID/RDX ---------------  Target Environment  -------------- Row 1 from 23
 Command ===>                                                  Scroll ===> CSR
                                                                              
 Primary commands: EXclude, SHow, Change, Find, Refresh, Hide, Size, REPort    
    Line Commands: S = Select I = Info X = Exclude U = Undo exclude            
                                                                              
 Automatic space calculation    ===> B + (N = No; M = MVS; D= DB2; B = Both)   
 Create target environment only ===> N   (N = No; Y = Yes)                     
                                                                              
 Extract File: TSOID01.FRSAMP.EXTMENU                                         
         SSID: DSN  Location: DSNLOCAT                                         
   Type      Object Name                                    SHOW     Status   C
   --------- ---------------------------------------------- -------- -------- -
 _ DATABASE  FRSMPDB                                                           
 _ TBLSPACE  **IMPLICIT**                                                      
 _ TABLE     TSOID01.CONTACT_TABLE                                            Y
 _  IX_REQ   TSOID01.CONT_IDX_Z                                               Y
 _ TBLSPACE  **IMPLICIT**                                                     
 _ TABLE     TSOID01.CUSTOMER_TABLE                                  Excluded Y
 _  IX_REQ   TSOID01.CUST_IDX_Z                                      Excluded Y
 _ TBLSPACE  **IMPLICIT**                                                      
 _ TABLE     TSOID01.ORDER_LINE_TABLE                                         Y
 S  IX_REQ   TSOID01.ORDL_IDX_Z                                               Y
 _ TBLSPACE  **IMPLICIT**  

To create the missing target objects:

In this field…

Do the following:

Automatic space calculation…

Enter B to let RDX calculate the space allocation parameters for MVS and Db2 objects.

Create target environment only

Type N to create the target objects and load them with the extracted data.

CMD

Type S next to the entry for ORDL_IDX_Z to view/edit the Create Db2 Index option.

Press Enter

File-AID/RDX displays the Create Index screen.

Field Names and Descriptions

Global Settings

The upper portion of this screen allows you to specify changes that apply to all listed Db2 or MVS objects.

FIELD

DESCRIPTION

Automatic Space Calculation

Specify globally whether you want File-AID/RDX to calculate the space allocation for new target objects based on the extracted data or not. The calculated space will not exceed the space allocation of the source. You can also set the status for individual objects. The plus (+) sign indicates that the status for one or more individual objects has been changed.

N

(No) The space allocation parameters for the new object will be the same as for the source object.

M

(MVS objects only) File-AID/RDX will calculate the space allocation for new target MVS files based on the extracted data.

D

(Db2 objects only) File-AID/RDX will calculate the space allocation for new target Db2 objects based on the extracted data.

B

(Both Db2 and MVS objects) File-AID/RDX will calculate the space allocation for new Db2 and MVS target objects based on the extracted data.

Create Target Environment Only

Specify whether you want File-AID/RDX to only create the target objects or also load data into the target objects.

N

(No) Loads the extracted data into the target objects.

Y

(Yes) File-AID/RDX will only create the target objects without loading any of the extracted data.

Lower Portion

The lower portion of this screen contains a list of Db2 and/or MVS objects and their indexes that File-AID/RDX will create prior to loading them. If there are more entries on the list than will fit in the screen, you can scroll the fields in the lower portion of the screen up and down using standard scrolling commands. Each object/index pair has its own two line entry.

Db2 objects to be loaded are listed in hierarchal and alphabetical order, starting with the database, listing all tablespaces within that database, all tables in the tablespace, all indexes, views, aliases, and synonyms for the table.

Important

Objects are only listed if they already exist in the target environment or the extract file contains their create DDL.

FIELD

DESCRIPTION

CMD

Enter the S (Select) line command in this column to edit the individual target index or path. Depending on the object, File-AID/RDX will invoke the “Create DB2 Index”, “Create VSAM AIX”, or “Create VSAM PATH” screen.

Type

The object type is indicated in the next column:

  • DATABASE indicates a Db2 database
  • TBLSPACE indicates a Db2 tablespace
  • TABLE indicates a Db2 table
  • TABLE_SYS indicates a Db2 SYSTEM TEMPORAL table
  • TABLE_BUS indicates a Db2 BUSINESS TEMPORAL table
  • TABLE_BIT indicates a Db2 BI-TEMPORAL table
  • TABLE_PAR indicates a Db2 partitioned table
  • FILE indicates an MVS sequential file, including GDG types
  • VSAM indicates an MVS VSAM KSDS file
  • IAM indicates an IAM (Innovation Access Method) file
  • AIX indicates an alternate index for an MVS object
  • PATH indicates a VSAM Path

Type

The following object types are only displayed if their corresponding table is marked to be created:

  • INDX indicates a secondary index for a Db2 table
  • IX_REQ indicates a required primary index for a Db2 table
  • IX_PAR indicates a partitioned index for a Db2 table
  • IX_P_REQ indicates a required partitioned index, either a primary, clustering, or index with UniqueRule of 'C' or 'R'. Indexes with Unique Rule of 'C' are required to enforce constraints and Indexes with a UniqueRule of 'R' are required for RI.
  • IX_P indicates a secondary partitioned index for a Db2 table
  • IX_DPSI indicates a data partitioned secondary index for a Db2 table.

Important

When creating an index: If the source is index-controlled, File-AID/RDX will create with table-controlled partitioning.

  • VIEWS indicates a view for a Db2 table
  • ALIAS indicates an alias for a Db2 table
  • SYNONYM indicates a synonym for a Db2 table

Object Name

Displays the fully qualified name of the object to be loaded. If it is a Db2 table it includes the creator ID of the owner of the table.

You can modify the entries in this column directly. Simply type the new name over the one displayed. You can also modify an object name in the Source to Target Mapping. There, you can modify the value in the Target field.

For Tablespace names only:
Do NOT Blank out the name of a tablespace to create the tablespace implicitly, instead select the table with the S line command and blank out the Tablespace field in the “Create Table” panel. File-AID/RDX generates DDL to create the tablespace implicitly as long as only one table is associated with the tablespace. The current SQLID must have the proper Db2 authority to create the tablespace in the execution phase.
For Database names only: File-AID/RDX does not support implicit Database creation; providing a Database name will continue to be a requirement for Create Tablespace and Create Table.

Show

Displays the result of the SHOW primary command. Depending on the specified parameter, the column name changes to and displays the associated Db2 DATABASE, STOGROUP, or TABLESPACE for the appropriate Db2 objects. This column is blank until you enter a SHOW command.

Status

Displays a status message for the object to be loaded.

C

(Create Object) Displays whether the object will be created (Y) during the load process or not (N).

Primary Commands

The following list identifies the primary commands that are available from this screen.

COMMAND

DESCRIPTION

CHANGE (C)

The CHANGE command allows you to globally update the target creator id for Db2 tables or target prefixes for MVS files. You need to specify the old string, new string and data type (both is the default.) If you enter the CHANGE command without any parameters, a pop-up window will prompt you for these parameters.

DOWN

Scrolls toward the bottom of the list of entries names by the specified scroll amount.

END

The END command returns to the Load Menu.

EXCLUDE (EX)

Enter the EXCLUDE command in the COMMAND field to exclude all source/target objects in the list displayed on the Object Load Specifications screen from the load. Use this command in conjunction with the U (Unexclude) line command or UNEXCLUDE primary command when you have a long list of source/target objects displayed and you want to include only a few source/target objects in the load.

The optional parameters DB2, IMS, and MVS limit the EXCLUDE command to one of the three object types.

FIND (F)

Searches the list for the specified string and scrolls the list to display the first matching entry at the top of the displayed entries. Use RFind to repeat the search.

HIDE (H)

Use the HIDE command to control which object types to hide from the displayed list. When entered without a parameter, HIDE displays the HIDE COMMAND window.

REFRESH (R)

Refreshes the list of objects of the Target Environment screen. Use the REFRESH command after changes to the listed objects have an influence on the hierarchal and alphabetical order of the display.

SHOW (SH)

The SHOW command alters the contents of the SHOW column in the Target Environment screen. Depending on the specified parameter, the SHOW column can display the associated database, tablespace or stogroup information for the appropriate Db2 objects in the list. SHOW without a parameter displays the SHOW COMMAND window.

SIZE (S)

Increases the scrollable area to display more entries at a time by hiding some of the screen header lines. SIZE is a toggle switch so enter SIZE again to return to the original format.

UNEXCLUDE (U)

Enter the UNEXCLUDE command in the COMMAND field to include all excluded source/target objects in the load again. Use this command in conjunction with the X (Exclude) line command or EXCLUDE primary command.

The optional parameters DB2, IMS, and MVS limit the UNEXCLUDE command to one of the three object types.

UP

Scrolls toward the top of the list of entries by the specified scroll amount.

Line Commands

The following File-AID/RDX-specific line commands are valid on this screen:

COMMAND

DESCRIPTION

E (Edit)

(Obsolete) Enter the E (Edit) line command for each index or path information you want to change. Depending on the object, File-AID/RDX will invoke the appropriate Create/Edit screen.

I (Information)

The I (Information) line command display the statements that will be used to create the object. For Db2 objects that will be the DDL, for MVS VSAM objects it will be the IDCAMS DEFINE and non-VSAM it will be the DD statement.

S (Select)

Enter the S (Select) line command for each index or path information you want to change. Depending on the object, File-AID/RDX will invoke the appropriate Create/Edit screen.

X (Exclude)

Enter the X (Exclude) line command for each index or path you want to exclude from the current auto create. Primary indexes may not be excluded.

Important

Excluding objects from the Auto Create process may compromise the load process.

U (Unexclude)

Enter the U (Unexclude) line command for each excluded index or path you want to include again in the auto create process.

Create Db2 Index

File-AID/RDX displays the Create Index screen illustrated in the following figure when you enter the S line command for a Db2 index in the Target Environment screen.

Create Index

File-AID/RDX ----------------- Create Index -----------------------------------
 COMMAND ===>                                                                   
                                                                               
                                                                               
 Primary Commands: PARTition, LimitKey                                     
                                                                               
 Source Object:                            SSID: DSN  Location: DSNLOCAT
  Index name . . . .: FRSAMP.ORDL_IDX                                           
  Table name . . . .: ORDER_LINE_TABLE                                          
  Index columns. . .: ORDER_NUM,ASC/ORDER_LINE_NUMBER,ASC                       
  Index Type . . . .: Non-partitioned                  
                                                                              
                                                                              
 Target Object:                            SSID: DSN  Location: DSNLOCAT
  Table name . . . .: TSOID01.ORDER_LINE_TABLA                                  
  Index Creator  ===> TSOID01                                                   
  Index name     ===> NEW_ORDL_IDX_Z                                           
  Index Type . . . .: Non-partitioned                  
                                                                               
  Automatic Space calculation  ===> Y   ( N = No; Y = Yes; M = Manual)   
                                                                              
   STOGROUP   ===> STG003     BUFFERPOOL ===> BP0                   
   PRIQTY(K)  ===> 0          FREEPAGE   ===> 0                  
   SECQTY(K)  ===> 0          PCTFREE    ===> 10 

To change the index name for the target object:

In this field…

Do the following:

Index Name

Type NEW_ORDL_IDX_Z.

Automatic Space calculation

Type Y.

STOGROUP

Specify one of your existing Db2 storage group.

PRIQTY(K)

Enter the number of kilobytes to be allocated for the file where your index will reside.

SECQTY(K)

Enter the amount of space (in kilobytes) to be allocated for the file if it exceeds the primary quantity.

BUFFERPOOL

Specify the Db2 buffer pool name associated with the index.

FREEPAGE

Specify the rate at which a page is left free when the index is loaded or reorganized.

Command

Type END to exit the Create Index screen.

Press Enter

File-AID/RDX returns to the Target Environment screen.

Field Names and Descriptions

The following list describes the fields on this screen.

FIELD

DESCRIPTION

SSID

Displays the Db2 subsystem ID of the extracted Db2 data.

Location

Displays the remote Db2 location name of the extracted Db2 data.

Index name

Displays the Db2 index name as it appears in the extract file.

Table Name

Displays the full Db2 object name, including creator ID of the table for the extracted index.

Index columns

Displays the Db2 column names that are used in the index.
If the index has an expression (IX_EXTENSION_TYPE field in SYSINDEXES equals 'S'), the expression(s) are listed here instead of the index columns.

Index Type

Displays the index type as specified in the extract file. Valid types are:

Non-Partitioned

Simple tablespace (No partitions).

Partitioned

Partitioned tablespace. The number of partitions are shown in the NUMPARTS field.

Data Partitioned Secondary

Data partitioned secondary index. The number of partitions are shown in the NUMPARTS field.

NUMPARTS

Displays the number of partitions.

SSID

Displays the Db2 subsystem ID of the “Target Environment”.

Location

Displays the remote Db2 location name of the “Target Environment”.

Table Name

Displays the full Db2 object name, including creator ID of the table for which you want to create the index.

Index Creator

Specify the creator ID of the index. This field is prefilled with the target creator ID for Db2 objects as specified in the Load Object Specification or Source to Target Mapping screen.

Index Name

Specify the name of the index. This field is prefilled with the extracted index name as specified or modified (pre- of suffix) in the Load Object Specification screen.

Index Type

Displays the index type as specified in the extract file. Valid types are:

Non-Partitioned: Simple tablespace (No partitions).

Partitioned: Partitioned tablespace. The number of partitions are shown in the NUMPARTS field.

Data Partitioned Secondary: Data partitioned secondary index. The number of partitions are shown in the NUMPARTS field.

NUMPARTS

Displays the number of partitions.

Automatic Space calculation

Displays whether you want File-AID/RDX to calculate the space allocation for new target index based on the extracted data or not. The calculated space will not exceed the space allocation of the source. It overrides the status set with the global “Automatic Space Calculation” field in the “Target Environment” screen. When this field displays an M, it indicates that the space allocation values have been entered manually which overrides the automatic space calculation.

STOGROUP

Specify the Db2 storage group in which the new index will reside. The storage group must already exist.

PRIQTY

Number of kilobytes to be allocated for the file where your index will reside.

SECQTY

Amount of space (in kilobytes) to be allocated for the file if it exceeds the primary quantity.

BUFFERPOOL

Specify the Db2 buffer pool name associated with the index.

FREEPAGE

Specify the rate at which a page is left free when the index is loaded or reorganized.

PCTFREE

Specify the percentage of each page left free when the index is loaded or reorganized.

Tablespace

Displays the number of partitions of the target tablespace. This field must not be blank or zero before attempting to define the partitions using the PARTITION command.

Original

Displays the number of partitions of the extracted index.

Primary Commands

The following File-AID/RDX-specific primary command is valid on this screen:

COMMAND

DESCRIPTION

PARTITION (PART)

Displays the “Index Partition Definition” screen which lets you define the attributes for each index partition, if the tablespace is partitioned.

LimitKey (LK)

Displays the “Limit Key Definition” screen which lets you define the limit key value for each logical partition, if the tablespace is partitioned.

Line Commands

There are no line commands available on this panel.

Related topics

Primary-commands-description

Line-commands-description

 

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