Modernizing the CA Datacom Data – SQL Access Part I
0 likes899 views
This document provides an overview of steps to modernize access to CA Datacom data by implementing SQL access. It discusses adding SQL attributes to the database model, defining AUTHIDs for SQL schemas, and using a SQL column report to determine legacy tables' SQL accessibility. The summary describes how implementing SQL allows critical business data to be accessed by new applications while existing applications continue functioning.
More Related Content
What's hot (20)
Viewers also liked (19)
Similar to Modernizing the CA Datacom Data – SQL Access Part I (20)
More from CA Technologies (20)
Recently uploaded (20)
Modernizing the CA Datacom Data – SQL Access Part I
- 2. 2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD © 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies. The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA. For Informational Purposes Only Terms of this Presentation
- 5. 5 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Why should we implement SQL? § SQL provides the basic access point for modern applications – ODBC/JDBC use SQL under the covers § Implementing SQL access on traditional data – Opens up critical business data to new applications and business functions – Does not interfere with existing traditional applications § Peaceful coexistence is much preferred to revolutionary change (rewrites) § Implementing SQL constraints on traditional data – Allows business rules to be enforced without requiring additional coding Modernization is the Key to Growth in Today’s World
- 7. 7 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL - AUTHIDs § AUTHIDs must be adding to the system before they can be used in table references § Default AUTHIDs provided with Datacom – SYSADM (system tables) – SYSUSR (default for user tables) § We recommend that the user define meaningful AUTHIDs for their environment – user_authid (18 character user specified name) Creating the System Level Schemas - AUTHIDs
- 8. 8 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL - AUTHIDs (Cont’d) Creating the System Level Schemas - AUTHIDs DBID AUTHID 0100 DB0100 0200 DB0200 1294 DB1294 • Using an AUTHID that ties to business function may make it easier to group the tables • All SQL table name must be unique with AUTHID • With multiple DBIDs per AUTHID be careful when assigning SQL table names AUTHID Business Function DBID Table PAYROLL Payroll 0100 All VENDOR Accounts payable 0200 VND, VNA, VN3 INVENTORY Sales and ordering 0300 0400 INV, ITM, DTL ORD, ODL, ITM • CA Datacom already requires 3 character table names to be unique within DBID • In this example we are using the DBID as part of the AUTHID as a simple default • Makes it relatively simple for existing users to remember the AUTHID
- 9. 9 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL - AUTHIDs (Cont’d) § AUTHIDs can be added to the system through various utilities – They only need to be defined once per environment (MUF) Creating the System Level Schemas - AUTHIDs Datadictionary batch Datadictionary online SQL statement
- 10. 10 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL – Database Model Adding SQL Names to the Database Model in PROD Status DD Entity Attribute Req. Values Default Status Comment Schema AUTHID No 18 Character No ADD CPY PROD Must be defined in PROD before using for tables Database SQL- Security No Y or N N UPD PROD Use default or set to N, Use external security SQL-NAME N/A 32 Character None UPD PROD Used for documentation only Area SQL-Name No 32 Character None UPD PROD Needed if adding new tables via DDL (CREATE TABLE … IN …)
- 11. 11 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL – Database Model (Cont’d) Adding SQL Names to the Database Model in PROD Status DD Entity Attribute Re q. Values Default Status Comment Table SQL-Intent Yes N, Y or R N UPD PROD Use Y for full SQL access Use R for SQL read access only AUTHID Yes Existing AUTHID None UPD PROD Must be already defined SQL-Name YES 32 Character None UPD PROD Must be defined to access table with SQL Key AUTHID N/A Assigned to table value auto UPD PROD Automatically assigned SQL-Name NO 32 Character None UPD PROD Must be defined to access index with SQL (ALTER or DROP)
- 12. 12 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Implementing SQL – Database Model (Cont’d) Adding SQL Names to the Database Model in PROD Status DD Entity Attribute Req. Values Default Status Comment Column AUTHID N/A Assigned to table value auto UPD PROD Automatically assigned SQL-Name NO 32 Character Generated UPD PROD Generated using existing column name Column AUTHID N/A Assigned to table value auto UPD PROD Automatically assigned SQL-Name NO 32 Character User specified UPD Test CPY PROD User wants specific SQL name User specified name for column requires extra steps
- 14. 14 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Making the SQL Attributes “Live” § SQL attributes are set through Datadictionary processes – SQL attributes made usable during the CXX CATALOG § SQL definitions are stored in the DDD § Only “active/production” definitions are in DDD Update TABLE Copy to PROD DDUPDATE MUF DD 0002 Catalog DDUPDATE MUF DD 0002 CXX DDD 0015
- 15. 15 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Legacy Data Structures § Legacy data structures may have some “SQL” access limits – All tables are accessible, but the content access may be limited § SQL accessibility to legacy table definitions – Group fields are ignored by SQL § Only elementary fields are viewable – 2nd redefinition columns are not accessible § Only the first set of column definitions are viewable; anything after the REDEFINE is ignored – Elements of repeating groups are not distinguishable § Repeating group (array) is represented as a single character column May Have Been Built Using Older Data Structures (VSAM, COBOL Copybooks)
- 16. 16 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD SQL Column Report § Can be executed against any existing table – Regardless of SQL-INTENT setting – Can be used to preview SQL accessibility Quick Way to Determine How SQL Accessible Legacy Table Definitions Are
- 18. 18 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD SQL Column Report (Cont’d) SQL ACCESS STD. - Shows Current SQL Accessibility STD – indicates if column is accessible by standard SQL NO - will include reason data is not accessible • CMP – column is a compound (group) field • RPT – Column is a repeating field • RDF – Colum is a redefinition (2nd definition)
- 20. 20 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD Recommended Sessions SESSION # TITLE DATE/TIME MFX92S Strategy and Vision for CA Datacom and CA Ideal™ 11/16/2016 at 12:45 pm MFX93S What’s new in CA Datacom 11/16/2016 at 1:45 pm MFX94S Reducing TCO with Datacom Compression (Presspack) 11/16/2016 at 3:00 pm MFX95SA Modernizing the CA Datacom data – SQL Access Part I 11/16/2016 at 3:45 pm MFX95SB Modernizing the CA Datacom data – SQL Access Part II 11/16/2016 at 4:30 pm MFX96S CA Datacom/AD Installation/Upgrade and Maintenance 11/17/2016 at 12:45 pm MFX97S CA Datacom/AD Report Utilization, and information gather for Support 11/17/2016 at 1:45 pm MFX98S Using CA SYSVIEW® to monitor and measure your CA Datacom environment – AD and DB 11/17/2016 at 3:00 pm MFX99S Birds of a Feather/Stump the Techie! 11/17/2016 at 3:45 pm