WebSphere logo Classic Federation Server for z/OS, Version 9.1
WebSphere logo Classic Replication Server for z/OS, Version 9.1
WebSphere logo Classic Data Event Publisher for z/OS, Version 9.1
WebSphere logo Data Integration Classic Connector for z/OS, Version 9.1


Table properties

Table properties are shown in the Properties view. You can use the Properties view to modify the properties of a table.

If the table already exists in a metadata catalog on a data server and you want any changes that you make to the table to be reflected in the metadata catalog, you must follow these steps:

  1. Drop the table from the metadata catalog. You can generate the DDL to drop the table by right-clicking the table and selecting Generate DDL. In the Generate DDL wizard, select the DROP statements check box.
  2. Run the generated DDL on the data server.
  3. Make your changes to the table.
  4. Generate the DDL to create the table. You can generate this DDL by opening the Generate DDL wizard and selecting the CREATE statements check box.
  5. Run the DDL on the data server.

The Properties view for a table contains the following information:

General page
Property Description
Name Type the name of the table.
Schema Displays the schema in the two-part name for the table.
Source DBMS Displays the type of DBMS in which the source data is located.
Change capture (For all data sources except CA-Datacom and DB2® for z/OS®)
Changes
Select this value if you want to use the table for change capture.
None
Select this value if you do not want to use the table for change capture.
XM URL For a native VSAM table that is being used for change capture, the name of the data space and the name of the Cross Memory (XM) queue to use. The change-capture agent that is capturing changes to the native VSAM table writes change data to this XM queue.

The format of the XM URL is XM1/name_of_data_space/name_of_queue

Columns page
Lists the columns of the table.
Source information page
The Source information page contains source information for:
Table 1. Source information for Adabas
Property Description
File DBID Optional: Type the identifier of the database in which the Adabas file is stored. This Adabas file is either the file that is identified in the File number field or the file that is referenced by the Predict view. The default value is 0. The identifier must be between 1 and 65535.
View name Type the name of the Predict view that describes the contents of an Adabas file that has fields that you want to map to columns. Classic Data Architect retrieves the Adabas Field Description Table (FDT) information for the Adabas file that is referenced by the view. If you want Classic Data Architect to access an Adabas file's FDT directly, do not provide a view name. Instead, provide the number of the Adabas file in the File number field.
Table 2. Source information for CA-Datacom
Property Description
Table name Type an identifier of 1 to 32 characters for the CA-Datacom table that the Classic table definition references. The name follows CA-Datacom/DB entity naming conventions.
Status/Version Select or type the status and version of the CA-Datacom table that contains the elements that you want to map to. The status and version can contain explicit values of TEST, PROD, HIST, or a value that begins with a T or H followed by a three digit number.
URT name Type the name of the User Requirements Table (URT) that is used to access the CA-Datacom table that contains the elements that you want to map to. The name must exist in a data set that is referenced by the servers STEPLIB DD statement or reside in the link pack area. The name follows z/OS load module naming conventions.

A URT must be provided on every request for service sent to CA-Datacom. Every service request is validated against an open User Requirements Table. This technique provides security (by restricting access) and efficient allocation of CA-Datacom resources. When you define your User Requirements Tables, consider the security implications. You must decide whether you want to have one User Requirements Table per CA-Datacom table that you map into the metadata catalog or have only a few User Requirements Tables for all CA-Datacom tables that you map into the metadata catalog. If you define only a few User Requirements Tables, you will have more relaxed security.

Table 3. Source information for CA-IDMS
Property Description
Subschema name Displays the name of the subschema that was obtained through a remote connection to the CA-IDMS database or from the local subschema file that you specified.
Schema name Displays the name of the schema that was obtained through a remote connection to the CA-IDMS database or from the local schema file that you specified.
Schema version Type a valid 4-digit integer between 0 and 9999 that, together with the schema name, uniquely identifies a CA-IDMS schema. The schema version follows CA-IDMS schema version naming conventions.
Data dictionary Type an identifier of 1 to 8 characters for the CA-IDMS database for the dictionary that contains the schema and subschema definitions. The data server binds to this dictionary to gather information from the schema and subschema when the data server creates the logical table. The identifier follows CA-IDMS database naming conventions.
Data database Type an identifier of 1 to 8 characters for the CA-IDMS database that contains the user data that the data server will access at runtime.
Access load module Type an identifier of 1 to 8 characters for the CA-IDMS batch access module to be used to communicate with the CA-IDMS central version that hosts the user data. The CA-IDMS identifier follows z/OS load module naming conventions.
VSAM information
RRDS
Specifies that a record in the subschema has a mode of VSAM and is not a member of a VSAM index set.
KSDS
Specifies that a record in the subschema either has a mode of VSAM and is a member of a VSAM key-sequenced data set, or has a mode of VSAM CALC.
ESDS
Specifies that a record in the subschema either has a mode of VSAM and is a member of a VSAM entry-sequenced data set, or has a mode of VSAM CALC.
Table 4. Source information for CICS VSAM
Property Description
FCT name Type the name of the CICS table that contains the information that is used by CICS file control for accessing the VSAM file.
Local APPLID Type a short identifier of 1 to 8 characters that designates the VTAM® LU 6.2 definition that a CICS region is listening on for connection requests. The CICS LUNAME corresponds to the value of the APPLID parameter that is specified in the system initialization definition (DFHSIT macro) of the target CICS subsystem where the VSAM file is located. The CICS LUNAME follows VTAM naming conventions.
CICS APPLID Type an identifier of 1 to 8 characters for the VTAM LU 6.2 definition that a CICS region is listening on for connection requests. This identifer corresponds to the value of the APPLID parameter that is specified in the system initialization definition (DFHSIT macro) of the target CICS subsystem where the VSAM file is located. This identifier follows VTAM naming conventions.
Logmode Type a short identifier of 1 to 8 characters for the name of the VTAM logon mode table that is used to control the session parameters for the conversation that is established between the local LU and the CICS LU. The logon mode table name corresponds to a z/OS load module that is accessible to VTAM. The definition for a Classic supplied logon mode table is supplied in SASCSAMP member CACCMODE.
Transaction ID Type a short identifier of 1 to 4 characters for the name of the supplied CICS transaction that is used for data access and validation purposes. The CICS transaction ID corresponds to the CICS TRANSACTION definition. Sample CICS transaction, connection, program, and session definitions are supplied in SCACSAMP member CACCDEF. The sample CICS transaction ID is EXV1 and can be modified.
Record exit Optional: Type a name for a record processing exit that is invoked to decompress sequential records when the file is accessed. The exit name given must exist in a data set that is referenced by the server's STEPLIB DD statement or reside in the link pack area. The exit name follows z/OS load module naming conventions.
Maximum length Type the maximum length (in bytes) of the buffer that is needed by the record exit to decompress a record.
Network name Type a short identifier of 1 to 8 characters for the name of the network where the CICS LUNAME resides, which corresponds to the CICS subsystem that is used to access a VSAM file. The NETWORK VTAM macro definition on the local image identifies the remote SNA network where the CICS subsystem resides. The network name follows VTAM naming conventions.
Table 5. Source information for DB2 for z/OS
Property Description
Creator Displays the schema of the table.
Table Displays the name of the table.
Subsystem ID Displays the ID of the DB2 subsystem in which the table is located.
Plan Displays the name of the DB2 application plan.

Accessing DB2 data requires binding an application plan for use by the DB2 Call Attach Facility (CAF) service. You can give the plan whatever name you want based on site-installation standards.

Type Displays the type of object that the new table is mapped to.

When you import a DB2 table into Classic Data Architect, you are creating a table that you can create in a metadata catalog. This field shows that the table is mapped to a DB2 table.

Table 6. Source information for IMS
Property Description
DBD name Displays the name of the IMS DBD (database definition) that the table references.
DBD type Displays the name of the IMS DBD (database definition) that the table references.
Leaf segment Displays the name of the leaf segment.
Index root Optional: Type a name for either of these two objects:
  • The physical or logical root segment of the IMS database that is identified by the DBD.
  • The perceived root segment of the IMS database of a secondary data structure that is created by a secondary index definition that exists in the DBD.
The default index root is the root segment of the physical or logical database that is referenced by the DBD.
IMS subsystem Optional: Type the 4-character name for the IMS subsystem that is used by the ODBA interface to access the IMS database that is identified by the DBD. The IMS subsystem ID is used only when the server is operating in an RRS two-phase commit environment. The IMS subsystem ID follows IMS naming conventions for subsystem identifiers.

The IMS subsystem ID must correspond to the value that is specified on the IMSID parameter on the IMSCTRL macro in the system definition of the target online IMS subsystem that is used to access or update the IMS data.

The IMS subsystem ID value is ignored for other forms of IMS data access (DRA or BMP/DBB/DLI) and when the table mapping is used for change capture.

PSB name Optional: Type the name of the PSB that is scheduled to access the IMS database that is identified by the DBD. This name is used if you are using a DRA or ODBA interface to access IMS data. The standard PSB corresponds to a PSB definition that is defined to the IMS online system that is being accessed. The PSB also corresponds to a PDS member under the same name in the active ACB library of the source IMS subsystem. The standard PSB name follows z/OS load module naming conventions.
Join PSB name Optional: Type the name of the PSB that is scheduled to access the IMS database that is identified by the DBD. The name is used if you are using a DRA or ODBA interface to access IMS data. The JOIN PSB corresponds to a PSB definition that is defined to the IMS online system that is being accessed. The PSB also corresponds to a PDS member under the same name in the active ACB library of the target IMS subsystem. The JOIN PSB name follows z/OS load module naming conventions. The JOIN PSB is scheduled when an SQL SELECT statement is executed that contains a JOIN predicate that references multiple IMS tables and this is the first table referenced in the JOIN.
Table 7. Source information for sequential files and native VSAM files
Property Description
DS Specifies that the information from which to create the table is contained in a data set.
DD Specifies that the information from which to create the table is contained in a data set with a DD name.
Name Type the name of the data set or DD card in which the information for the table is located.
Record exit Type the name of a record processing exit that is invoked to decompress sequential records when the file is accessed. The exit must exist in a data set that is referenced by the servers STEPLIB DD statement or reside in the link pack area. The exit name follows z/OS load module naming conventions.
Maximum length Type the maximum length (in bytes) of the buffer that is needed by the record exit to decompress a record.
Source columns page
Lists the columns in the table.
Path information page (for CA-IDMS only)
Lists the records and sets with elements that are mapped to columns in the table.
Source elements page (for CA-IDMS only)
Lists the elements that are mapped to columns in the table.
Source fields page (for IMS only)
Lists the fields that are mapped to columns in the table.
Segments page (for IMS only)
Lists the segments that contain fields that are mapped to columns in the table.
PCB selection page (for IMS only)
Displays the method that Classic federation will use to select PCBs for accessing the table.
Privileges page
Lists that privileges that are granted on the table. Click the add button (Plus sign) to add privileges. Click the delete button (Delete button) to remove privileges.
Documentation page
Lets you add comments to the table.
Related tasks
Adding or replacing columns in tables based on copybooks
Modifying the selection of records in tables for CA-IDMS databases
Mapping tables and creating publications for Classic event publishing
Mapping tables for Classic federation
Mapping tables for Classic replication
Related reference
Column properties
Database properties
Publication properties
Publishing queue map properties
View properties
Index properties
Stored procedure properties


Feedback

Update icon Last updated: 2006-12-15