Verifying Installation

Starting Your Product › Preparing to Start CA Gen › Preparing to Start z/OS Implementation Toolset › Verifying Installation

Verifying Installation

Verifying IT installation is a matter of processing a sample set of Implementation Packages (IPs) from the distribution media CEHBSAMP. IPs are created on an CA Gen code generation platform and contain an Installation Control Member (ICM file) and source code. There are three types of IPs: load module, RI trigger, and DDL.

Load module IPs contain code for an CA Gen application load module. Both standard and enhanced screen types are provided as samples. Load module IPs provide IPs for DBMS targeting DB2. The RI trigger IP contains the code to implement referential integrity for a model. The DDL IPs contain the IDCAMS statements (if storage groups are not used) and SQL to build the application’s database. There are additional DDL IP that uses storage groups that you can use instead. The following table shows the contents of the CEHBSAMP.

IP Name	Description
TIXIVPDB	Sample DDL IP targeting DB2– VSAM
TIXIVPDS	Sample DDL IP targeting DB2 – Storage Groups
TIXIVPRI	Sample RI trigger IP targeting DB2
TIXIVPIB	Sample load module IP for IMS BYPASS STANDARD
TIXIVPBE	Sample load module IP for IMS BYPASS ENHANCED
TIXIVPIM	Sample load module IP for IMS MAPPED STANDARD
TIXIVPME	Sample load module IP for IMS MAPPED ENHANCED
TIXIVPTS	Sample load module IP for IEFAE STANDARD
TIXIVPTE	Sample load module IP for IEFAE ENHANCED
TIXIVPCI	Sample load module IP targeting DB2 for CICS STANDARD
TIXIVPCE	Sample load module IP targeting DB2 for CICS ENHANCED

There are five procedure steps for each IP. The procedure steps are packaged into one IP to create one load module. All five transactions should point to the program name MENU.

Before you can process the IPs, the following conditions must be met:

The Implementation Toolset components must be installed on your target system, according to the instructions in the preceding sections.
A load module script and RI trigger script must be loaded for each target supported at your site (TSO, IMS and CICS ). For more information about loading load module script and RI trigger, see the z/OS Implementation Toolset User Guide.
A target environment must be configured for each target supported at your site (TSO and IMS targeting DB2 or, CICS targeting DB2). For more information about configuring a target environment, see the z/OS Implementation Toolset User Guide.
The libraries referenced for the target environment must exist. Member TIXIVPLB in the IT JCL library can be used to allocate these libraries.