|
|
|
To implement ReportCenter with a new CA Datacom/AD environment, perform the following steps:
Note: If the CA Common Services for z/OS components are already installed, you do not have to reinstall them. You should run CA Common Services for z/OS r11 with SP6 applied as the minimum.
After this step, your complete CA Datacom/AD environment is customized and ready for use with ReportCenter.
Important! During these steps, you may need to customize some WRDCM* members. Do not edit them directly. These members are maintained by SMP/E; therefore, future maintenance will overwrite your changes. Copy these members to another data set before editing.
CA Common Services for z/OS is a collection of MVS utilities that provides common system functions to CA mainframe products.
Different products can require different CA Common Services for z/OS components. After you install a Common Services component for use by one CA product, you do not have to reinstall it for another product.
CA Datacom/AD and CA Datacom Server require the following components:
The Resource Initialization Manager. Also required by CA NetMaster products.
The Event Notification Facility.
The Common Communications Interface.
The Common Language Runtime Facility.
The Virtual Processing Environment.
Notes:
You may already have all or some of these components installed. To find out which components are installed on your system, run an SMP/E QUERY against the CSI where you installed CA Common Services for z/OS. You can run the query using online facilities or a job similar to the following:
//jobname JOB .............. //* //APPLY EXEC PGM=GIMSMP,REGION=0M,PARM='DATE=U' //SMPCSI DD DISP=SHR,DSN=?prefix.SMPCSI.CSI //SMPHOLD DD DUMMY //SMPLOG DD DUMMY //* //SMPCNTL DD * SET BDY(GLOBAL). LIST GLOBALZONE. /* LIST INSTALLED FMIDS */ /*
Compare the FMIDs listed in the CA Common Services for z/OS documentation with the installed FMIDs listed by your query. If you have installed all the CA Common Services for z/OS components in the table, you are ready to install the CA Datacom/AD environment.
Note: Ensure that you enter the CCI system ID in the ReportCenter implementation worksheet.
If there are any required CA Common Services for z/OS components that are not installed, install these missing components. These components are supplied on the CA Common Services installation tape—they are not supplied with CA NetMaster or CA Datacom/AD.
Note: For more information about installing the missing components, see your CA Common Services documentation.
Some details from your CA Common Services for z/OS installations, including data set names and parameters, are required during the ReportCenter CA Datacom/AD implementation.
The CA Datacom/AD environment is installed separately from the ReportCenter installation and setup steps. The CA Datacom/AD environment uses its own installation tape.
The JDBC interface CA Datacom Server is automatically installed when you install the CA Datacom/AD environment.
Note: For information about installing the CA Datacom/AD environment, the CA Datacom tape contents, tailoring the CA Datacom products, maintenance procedures, and troubleshooting, see the CA Datacom/AD Installation and Maintenance Guide. Not all this information is relevant to ReportCenter. All information that is required to tailor CA Datacom/AD for use by ReportCenter is contained in this guide.
To install the CA Datacom/AD environment, perform the following steps:
Important! Run the installation jobs AX22MKD and AX23CSIU to set the path where the HFS modules are installed. Also, install jobs AAX3REC, AAX4APP, and AAX5ACC are supplied with an END OF JOB statement ‘//’ placed between the non-HFS SMP/E JCL and the HFS SMP/E JCL. Ensure that you remove this card when running the jobs to facilitate HFS installation.
Review the information provided in the CA Datacom/AD Installation and Maintenance Guide. The CA Datacom/AD documentation refers to the region executing the CA Datacom environment as a Multi-User Facility or MUF.
The following are of particular importance:
Review the information about the use of the IBM CBIPO program. Most sites have this utility available and use it to perform the JCL changes to reduce installation time and JCL editing requirements. There can be up to 18 separate jobs involved in this installation, so it is worth the time to use this utility.
Review the information about the CA Datacom/AD SVC. The CAIRIM installation of the CA Datacom SVC is required unless you have CA Datacom/AD r11 installed on the system on which you are going to install your new CA Datacom/AD environment. One CA Datacom SVC can support up to 256 environments. Contact Technical Support for advice about sharing a single CA Datacom SVC.
References to requirements for CA Datacom on the use of CICS can be ignored.
Install CA Datacom/AD on the system where you run the ReportCenter Java Task and the ReportCenter control region.
Note: If the image is in the same sysplex, you can run the AD environment on a different z/OS image (from the ReportCenter control region). This setup is more complex. If you must implement this environment, contact Technical Support.
For information about installing the CA Datacom/AD environment, see the CA Datacom/AD Installation and Maintenance Guide.
Because many products can use the CA Datacom/AD environment, the installation is separated into the following sections:
To install CA Datacom/AD for use with ReportCenter, complete the procedures described in the following sections:
The sections in the CA Datacom/AD Installation and Maintenance Guide describe the jobs required to load the CA Datacom/AD code from tape, perform SMP/E functions, add the CA Datacom/AD SVC, and perform essential internal DBMS setup functions. Run these jobs as directed.
Review the maintenance level required for CA Datacom/AD. If the service pack level of the installed product does not include the required maintenance, you must install the maintenance separately. You can obtain the required maintenance from Technical Support.
To install the maintenance
The CA Datacom/AD Installation and Maintenance Guide includes several batch jobs that you can run to verify that the AD installation is operational before customizing the environment for ReportCenter.
ReportCenter does not use the COBOL utilities used by these jobs; you should run all of these verification steps because they uncover any problems with the basic DBMS installation.
To create site-standard jobs for starting, stopping, and backing up the CA Datacom/AD environment, see the recommended steps in the CA Datacom/AD Installation and Maintenance Guide.
The sample database startup is provided as a long running job, but this can be made a started task if this is more suitable for your site. If you plan to use a batch job to start the database, ensure that the TIME=1440 parameter is set on the execute DBMUFPR step.
ReportCenter uses a database that is installed into the CA Datacom/AD environment. The database is used to store reporting data collected by your ReportCenter regions. This database is empty until you begin your own data collection.
Important! The CA Datacom/AD environment must be installed before you install the ReportCenter database. This is because the installation tasks require an active CA Datacom/AD environment.
During the CA Datacom/AD installation tasks, you edited and saved the JCL member ADnSTRT, where n is the release number of CA Datacom/AD that you are using. This member starts the CA Datacom/AD environment. The environment must be running before you run any ReportCenter database installation jobs.
Important! You must start the MUF before performing these tasks.
Each database accessed by SQL in CA Datacom/AD has an SQL schema name.
To ensure that the table names used by CA NetMaster are not duplicates of any other tables, create a specific schema for ReportCenter.
To create the ReportCenter schema in the CA Datacom/AD environment
This job creates the ReportCenter database schema (PRODRPTS).
Note: After the ReportCenter schema is defined, you never have to add it to this AD environment again. If you run this step a second time, you receive an SQLCODE of -118 with a DSF return code of NAAE (already exists).
The ReportCenter database is defined to the CA Datacom/AD environment by using a batch utility program that is provided with the environment. The batch utility defines the ReportCenter database (with the schema name of PRODRPTS), and the tables needed to support ReportCenter.
To define the ReportCenter database and tables to the CA Datacom/AD environment
This job executes the CA Datacom/AD DDUPDATE batch utility.
Note: This job may be resubmitted, as required, until it completes successfully.
After the database is defined, you should not need to define it to the environment again. You can redefine the database definition, if needed; however, this should be done only under instructions from Technical Support.
When the ReportCenter database is defined, you must catalog the database definition, using the DDRTVCAT batch utility provided by the CA Datacom/AD environment. This utility validates the database definition to make sure it matches the current ReportCenter database model, and then catalogs it to the environment. After it is cataloged, the database is available for processing under the CA Datacom/AD environment.
To catalog the ReportCenter databases and tables
This job executes the CA Datacom/AD DDRTVCAT batch utility.
Note: This job may be resubmitted, as required, until it completes successfully.
After the database is cataloged, you should not need to catalog it to the environment again. You can recatalog the database definition, if needed; however, this should be done only under instructions from Technical Support. Rerunning the catalog of an active database definition can cause existing data in that database's tables to be marked unusable and result in a loss of existing data.
When you have defined and cataloged the database, you must allocate a set of data sets to hold the data (and indexes) for the ReportCenter tables.
To allocate the database data sets
This job executes the IBM IEFBR14 batch utility.
Note: This job contains the space allocations for all the database table files. The defaults should be sufficient for all but the largest sites. For more information, see CA Datacom/AD Space Sizing Considerations.
Note: This job may be resubmitted, as required, until it completes successfully.
When you have allocated the data sets, you must format them ready for use as database tables.
To initialize the data areas and prepare the ReportCenter tables
This job executes the CA Datacom/AD DBUTLTY batch utility. This utility formats (INIT) each of the data sets and marks them null loaded (loaded with no rows).
Note: This job may be resubmitted, as required, until it completes successfully.
Database constraints include, for example, foreign key and check constraints. These constraints function as rules that the database management system enforces to ensure the integrity of the data.
To add the ReportCenter database constraints
This job executes the DBSQLPR dynamic SQL program that processes the SQL commands that add the constraints to the production and sample databases. It also primes the production database KEYRANGE table with zero values and loads the TIMEFRAME table with all the necessary valid time ranges used in report generation.
Note: This job can be resubmitted, as required, until it successfully completes. When this job completes, the constraints remain in place until the table is dropped. Any attempt to add these constraints fail with an SQLCODE of -118 with a DSF Return Code of NAAE (already exists).
During the CA Datacom/AD installation, you are instructed to run the database backup job. This job creates backups of the CA Datacom/AD environment, which includes everything except the data stored in the ReportCenter database. Following the successful implementation of the ReportCenter database, you must re-execute this database backup job.
Note: To back up the ReportCenter database, use the supplied job WRDCMUNL. To restore the RerportCenter database, use the supplied job WRDCMREL.
In addition, these jobs must be standardized for your environment and added to the regularly scheduled system backups. These backups are needed in case the system fails or you accidentally delete one of the data sets. If this occurs, contact Technical Support for assistance in restoring the required data sets.
The CA Datacom Server is positioned between the ReportCenter Java Task and the CA Datacom/AD environment, and provides CA NetMaster with access to its databases. A ReportCenter Java Task service sends an SQL request to CA Datacom Server. The server passes the request to CA Datacom/AD and then passes the results back to the ReportCenter Java Task.
CA Datacom Server has the following components:
Runs as a job or started task. The code is installed automatically with CA Datacom/AD.
Is Java and C code that the ReportCenter Java Task invokes. The code is stored as HFS files and runs in the USS environment. This code is installed with your CA Datacom/AD installation.
To set up your CA Datacom Server production jobs
This runs the CA Datacom Server mainframe server component.
If you plan to use a batch job to start the server, you must ensure that the TIME=1440 parameter is set on the execute step.
Note: Started task ENF must be running because this supplies all of the CCI modules required to enable the server to connect to the database.
To start the CA Datacom Server
DSV00049I-CA Datacom Server Option 5.0 0000 INITIALIZED - NETMASTER
If this job does not start or initialize correctly, contact Technical Support.
If the job fails with CC=16, ensure that your CA Datacom/AD job is active and has completed initialization.
| Copyright © 2012 CA. All rights reserved. |
|