Using CA Dataquery with CA Datacom Transparencies

Using CA Dataquery with CA Datacom Transparencies

If you want to use CA Dataquery to access databases that have been migrated using the CA Datacom VSAM Transparency, the CA Datacom DL1 Transparency, or the CA Datacom TOTAL Transparency, you must look at your CA Datacom Datadictionary definitions and consider your plans to use INSERT, UPDATE, or ERASE.

VSAM Transparency

If you plan to use CA Dataquery to access databases that were migrated using CA Datacom VSAM Transparency, ensure that you have meaningful names for column and keys in CA Datacom Datadictionary or that you create aliases that are meaningful to your users.

CA Dataquery does not use the "occurs depending on" information to process variable-length rows. Be careful when you reference an occurring column in a query to ensure that the subscript is in the range of the depending on column's value. CA Dataquery always processes the rows as if they were the maximum row length.

See your CA Datacom VSAM Transparency documentation for more information.

DL1 Transparency

If you plan to use CA Dataquery to access databases that were migrated using CA Datacom DL1 Transparency, you should do the following:

• Ensure that you have meaningful names for columns and keys in CA Datacom Datadictionary or that you create aliases that are meaningful to your users.
• Define additional columns and keys to CA Datacom Datadictionary.
• Redefine the CA Datacom DL1 Transparency prefix column in CA Datacom Datadictionary to maintain the delete bits.
• Redefine the concatenated keys (PPCK, LPCK) into individual columns in CA Datacom Datadictionary so that you can do joins.
• Ensure that the integrity of the migrated data is not compromised if you use INSERT, UPDATE, or ERASE. CA Dataquery is not aware of the special DL1 relationships in the data.

See your CA Datacom DL1 Transparency documentation for more information.

TOTAL Transparency

If you plan to use CA Dataquery to access databases that were migrated using CA Datacom TOTAL Transparency, you should ensure that:

• You have meaningful names for column and keys in CA Datacom Datadictionary or that you create aliases that are meaningful to your users.
• The integrity of the migrated data is not compromised if you use INSERT, UPDATE, or ERASE. CA Dataquery is not aware of the special relationships in the data.

See your CA Datacom TOTAL Transparency documentation for more information.