System Requirements for Mainframe Installation
Verify the following prerequisites and system requirements before you install mainframe components:
Verify the following prerequisites and system requirements before you install
Test Data Managermainframe components:
General system requirements for mainframe access on the
Test Data Managerserver are as follows:
- COBOL/LE runtime libraries
- Access to site JCL standards to customize delivered JCL to site requirements
- FTP access to the Mainframe to move both installation files and generated objects between the Mainframe and the distributed platforms where theTest Data ManagerGUI runs
- User privileges to perform TSO RECEIVE on the XMIT files and allocate the required libraries in the chosen dataset High Level Qualifiers (HLQ)
- Permission to submit and manage tasks and jobs through SDSF panels or the equivalent, or to have permission to issue operator commands to purge (/P) or start (/S) tasks/jobs
z/OS DB2 Access
General requirements for integrating with a DB2 database are as follows:
- DB2 v10 or higher subsystem (with active WLM address space for standard ODBC / JDBC calls)
- ODBC connectivity to z/OS DB2
- JDBC Type 4 connectivity to z/OS DB2
- Access to run DB2 programs through TSO program IKJEFT01 or the equivalent, and DB2 utility program DSNTIAUL
- Installation user privileges to create tables, bind DBRMs, import data, and grant access to users and programs
Data storage requirements for integrating with a DB2 database are as follows:
- Data is stored as Single Byte Character Set (SBCS). This can be either EBCDIC or UNICODE (providing each character is stored in a single byte).
- Data stored in Double Byte Character Sets (DBCS), for example Graphic fields, is not supported.
- Data stored in Multi Byte Characters Sets (MBCS / UNICODE) that have characters stored in more than 1 byte, is not supported.
- Data stored in LOBs, CLOBs, BLOBs, are not natively supported. (Potential for unloading structured LOB data to a flat file for processing.)
DB2 Database Driver Installation
CA Technologies does not provide ODBC / JDBC drivers for connection to DB2. Install, license and configure the following drivers on the
Test Data Managerserver.
- DB2 Connect for connectivity to z/OS DB2 data from theTest Data ManagerGUI.Note: No license is required for the IBM Data Server Client Version 10.5 Fix Pack 5 client software to fetch data from DB2 LUW. However, an IBM DB2 Connect Enterprise Edition 25 Authorized User License is required for this client software to connect to DB2 on mainframe. The IBM part number for this Enterprise Edition license is D58FILL. The ODBC and .NET drivers provided with this licensed client software are used byTest Data Managerand by the TDoD Web Service, respectively.
- DB2 Type 4 JDBC for connectivity to z/OS DB2 from the GTSubset and FDM UIs.
- If you are using ODBC or the DSNless ODBC connection type, and your ODBC driver is version 10.5 or below, and Datamaker encounters problems connecting to DB2 on mainframe, we recommend you upgrade the ODBC driver to 11 or the latest version.
Access to VSAM, Sequential Files, and Other z/OS Data
Test Data Managerrequires access to copybooks that describe the VSAM, PS files, IMS DL1 segments, or access to other z/OS data unloaded to file for processing.
IMS Database Access
Test Data ManagerMainframe IMS Add On package includes an entitlement to a restricted version of CA File Master Plus for IMS 12.0. This version of CA File Master Plus for IMS lets test data engineers perform the following actions:
- Browse IMS database content
- Filter IMS content and view or update a record layout
- Extract IMS database records to a sequential file
- Reload IMS database content from a sequential file
- Automate the IMS data extract and load process using batch jobs
Other CA File Master Plus for IMS activities are restricted, and use of the product entitlement is only allowed for test data management activities. However, if you already own the full version of CA File Master Plus for IMS 12.0, you do not need to install this restricted version. You can use an existing installation of CA File Master Plus for IMS 12.0 for test data management activities as well.
See the following pages in the CA File Master Plus for IMS documentation for installation and configuration instructions:
- Installation: File Master Plus 12.0 - Installing
- Browse IMS Database Content: File Master Plus 12.0 - ISPF - Browsing IMS Databases
- Extract IMS Content: File Master Plus 12.0 - ISPF - Using Utility Functions
- Reload Extract Files into an IMS Database: File Master Plus 12.0 - ISPF - Using Utility Functions - Reload Utility
- Generate Extract File Record Layouts: File Master Plus 12.0 - ISPF - Using Utility Functions - Extract Layout Utility
- Manage Record Layouts: File Master Plus 12.0 - ISPF - Working with Record Layouts
You can also use a third-party product that provides the following functionality to access IMS v15 data for CA TDM activities:
- Ability to subset IMS data on segment or field level, or both (semi-complex subset rules)
- Extract to a flat file structure
- Records in the flat file are defined by a valid copybook structure (Test Data Manageruses it to access the fields in the file)
- Ability to Load or Replace segments from the "masked" flat file into IMS
- Copies of DBD and PSBs for the segments being processed
You can use a third-party product, but CA does not provide any support for any third-party product for IMS data access.
Other Prerequisites and Considerations
Before installation, review the following requirements with the relevant sections of your organization:
- Mainframe High Level Qualifier (HLQ) to RECEIVE the XMIT files. The default is GRIDT01, and the JCL uses this HLQ. If the HLQ is changed to another name, amend the provided JCLs.Note:If you use HLQ, ensure that HLQ is defined within SMS ACS. The installation is received into its own distinct HLQ directories and does not affect system directories or files. You also require access to the HLQ file structure for the required IDs.
- Review JCL job names, message classes, and job classes for the JCL submissions such as masking and subsetting. Ensure that the relevant IDs have access to submit and manage the results. Also ensure access to issue operator commands to purge (/P) or start (/S) jobs and tasks using SDSF or the equivalent.
- Seed data can be held within either:
- DB2 tables — This option is preferred for all sites with DB2 installed. It is required for masking and subsetting of DB2 data.Before you install, determine the subsystem and schema name for the product reference tables. GRIDT01 is the default schema.
- VSAM files — This option is for clients with no DB2 installation and no requirement for masking or subset of DB2 data.
- The best roles to complete the noted tasks are DBAs or Systems, Programmer, or Operations Analyst. Plan and raise change control well before the installation date.
- Minimal disk space (<1 cylinder) is required for each library. A few megabytes are required for the VSAM or DB2 seed data.
For assistance, contact product support.