COPE Dictionary - Documentation for BMC COPE 19.02
Matthew Perez Internal COPE Dictionary Tables (Option 4.10)
COPE maintains several ISPF tables that contain information about the environment. The tables are used to rename objects and to coordinate various activities during the generation process.
Before describing the display facilities, a brief description of the way information is maintained in the tables will be given. COPE uses ISPF tables to store many types of records. The type of record is maintained in a variable named Rowtype. If a table only has a single type of record, there is no row type field defined in the table.
All fields for a particular Rowtype are normally stored as extension variables (see the IBM ISPF Programmers Guide for an explanation of extension variables).
COPE uses a convention for storing hierarchical information. The convention is top to bottom, left to right. For example, if segment types B and C are children of type A then the rows are stored as:
ABB C C A B
etc.
Note
If this convention is not followed when segments are changed, COPE facilities will not operate correctly.
Multi segment tables always have a single "root" row followed by a hierarchy of rows as described above. For problem analysis, there may be a requirement to display the contents of the control tables. For example, you may want to translate "real" names to C-numbers or vice versa.
Warning
C-numbers are often reserved for objects but never used, so do not take the presence of a C-number as an indicator that a corresponding member must exist. It may not.
The contents of tables and their field-names may be dumped into a dataset for editing see "Viewing Table Contents in Edit", however tables may also be displayed in a more structured edit application (for a description of the details of the Table Editor see Viewing Table Contents in Edit).
Some of the tables may be displayed by entering 4.10 (Dictionary) on the primary panel. The following menu will be shown.
Dictionary Table Selection Menu DB/TM
Dictionary Table Selection Menu DBCTL:
Dictionary Table Selection Menu DCCTL:
Additional tables may be viewed by entering 11 on the Primary Table Selection Menu.
The following table lists the Table options:
Not all options are available in all environments.
Option | Description |
|---|---|
4.10.1 | Table of all PSBs, their COPE C-numbers and their usage (Same display as 4;PSB;GB) |
4.10;2 | Imported DBDs and their assigned C-numbers for DBD and DD names |
4.10.3 | Imported DFSMDA (Dynalloc) definitions |
4.10.4 | Stage 1 table summary |
4.10.5 | Table of PSB name and default C-number Plan names |
4.10.6 | Imported MFS names and their COPE assigned MID and MOD names |
4.10.7 | DBDs and their assigned COPE C-number (subset of 4.10.2 table) |
4.10.8 | Table of DBD,FILE,AREA names for DEDB definitions |
4.10.9 | Table of DBD,FILE,AREA,C-number names |
4.10.10 | DB2 collection names used in COPE plan conversion |
4.10.11.1 | Explicitly related DBDs for all systems |
4.10.11.2 | Cross reference of PSBs and the DBDs they reference together with the C-numbers of each (This table must be generated by a batch job) |
4.10.11.3 | BMP and Batch PSB and their COPE C-numbers |
4.10.11.4 | PSBs excluded with B;4;2;XPSB application |
4.10.11.5 | Excluded definitions from Option 1.7 |
4.10.11.6 | On-line (MPP IFP) PSBs and their C-numbers |
4.10.11.7 | BMP PSBs and their C-numbers |
4.10.11.8 | Excluded DBDs for PSBs defined with the B;4;2;XPSB application |
4.10.11.9 | Table of all DBDs and their COPE C-numbers for all systems |
4.10.11.10 | Table of related program names (not-used) |
4.10.11.11 | This option has been disabled |
4.10.11.12 | Table of areas and COPE assigned C-numbers for DEDBs |
Viewing Table Contents in Edit
The COPE dictionary contains many tables and many fields. The best way to understand the contents of the tables is to dump the contents so that the data is displayed together with the field name it is contained in.
COPE tables are addressed by a 4 part name PROJECT.GROUP.TYPE.NAME. There are Project related tables and System related tables. System tables have a $ value for PROJECT and LEVEL. Project tables use the PROJECT and GROUP values associated with an Lsys.
Option 5.8 allows COPE dictionary tables to be dumped. The following menu is displayed.
Table Dump Specification Menu
If P is entered in the command field and the PROJECT, GROUP, TYPE and NAME fields are completed, a table will be retrieved and dumped to a dataset.
Enter E to review the dump.
Table Dump Example
The number of rows in the table is displayed. The field names associated with the data is displayed in a box. The number to the left of the field names is the value of the ROWTYPE field. The data values are aligned under the field names. The ROWTYPE of the row that the data was extracted from is displayed on the left.
There following is a table of PROJECT, GROUP, TYPE, NAME table access values and a description of the table that is accessed.
PROJECT | GROUP | TYPE | NAME | TABLE DESCRIPTION |
|---|---|---|---|---|
$ | $ | $ | $ | System Index. This table contains the C-number table name of all System tables |
$ | $ | ACTIVE | ACTIVE | Table of active systems |
$ | $ | ADDPSB | ADDPSB | Table of C-numbers by Lsys for BMP applications |
$ | $ | HALDB | ALL | Table of C-numbers for HALDB Databases and Partitions |
$ | $ | ALLACB | ALLACB | Table of all PSB together with their usage and C-numbers |
$ | $ | ALLSTAG | ALLSTAG | Table of combined SDELTA Stage 1 attributes |
$ | $ | BMP | BMP | Table of all BMP applications and their C-numbers |
$ | $ | COPEIMS | COPEIMS | Table of Logical Systems and Dynalloc and Stage 1 sharing attributes |
$ | $ | COPEPR | COPEPR | Project/Group definition table |
$ | $ | MASS | DBD | All DBD from all Logical Systems with their DBD and DD C-numbers |
$ | $ | DESCDBD | DESCDBD | Able of information used by the COPE IMS SS application |
$ | $ | DISPLAY | DBD | Index table used by 3;DBD application |
$ | $ | DISPLAY | PSB | Index table used by 3;PSB application |
$ | $ | DISPLAY | MFS | Index table used by 3;MFS application |
$ | $ | EXCLUDE | EXCLUDE | PSBs excluded with B;4;2;XPSB application |
$ | $ | INCLUDE | EXCLUDE | Excluded databases and transactions and applications from 1;7 application |
$ | $ | TRANPSB | TRANPSB | Table used by B;5;4 X-Ref application containing all defined transactions and databases |
$ | $ | Lsys-name | DBD | DBD names and their associated DBD C-numbers and DD C-numbers |
$ | $ | Lsys-name | DDELTA | Deleted Stage 1 statements |
$ | $ | Lsys-name | DYNALLOC | DFSMDA (Dynalloc) definitions |
$ | $ | PGM | Lsys-name | PSBs and their assigned C-numbers |
$ | $ | SDELTA | Lsys-name | Stage 1 deleted statements |
$ | $ | STAGE1 | Lsys-name | Stage 1 source |
$ | $ | S1DELTA | Lsys-name | Stage 1 statement attributes |
$ | $ | MFS | Lsys-name | MFS NID and MOD names and their COPE names |
$ | $ | LEVSTRUC | LEVSTRUC | Hierarchical information for defined Logical Systems |
$ | $ | LOGICDBD | LOGICDBD | Table of explicit logical relations between databases for all Logical Systems |
$ | $ | PGMREN | PHYSYSXX | (The XX is the XCOPEINU ZDEFAULT value) Table of Logical Systems the PSBs are defined in |
$ | $ | STG1 | TERMINAL | Non APPLCTN,DATABASE,TRANSAVT Stage 1 statements |
$ | $ | XCMNSTG1 | STAGE1 | Stage 1 source for XCMNSTG1=YES ZDEFAULT definition |
$ | $ | XREF2TAB | XREF2TAB | Entities and their C-number generated by the Stage 1 generation process and used for the REFRESH processes |
PROJECT | GROUP | DBD | $ or NAME | (Index if $ specified) Parsed DBD information |
PROJECT | GROUP | DBDCOPY | $ or NAME | (Index if $ specified)DBDCOPY definitions member list |
PROJECT | GROUP | DBDSRCLB | $ or NAME | (Index if $ specified) DBD source definitions member list |
PROJECT | GROUP | MFS | $ or NAME | (Index if $ specified) Parsed MFS information |
PROJECT | GROUP | MFSCOPY | $ or NAME | (Index if $ specified) MFSCOPY definitions member list |
PROJECT | GROUP | MFSSRCLB | $ or NAME | (Index if $ specified) MFS source definitions member list |
PROJECT | GROUP | PSB | $ or NAME | (Index if $ specified) Parsed PSB information |
PROJECT | GROUP | PSBCOPY | $ or NAME | (Index if $ specified) PSBCOPY definitions member list |
PROJECT | GROUP | PSBSRCLB | $ or NAME | (Index if $ specified) PSB source definitions member list |
List Excluded Databases (Option B;4.2.LDX)
When PSBs are excluded, all databases that the PSBs refer to are also excluded together with all those databases' indexes or logically-related databases.
The LDX command displays excluded DBD names as follows:
LDX Display of Excluded DBDs
