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

Tips

This section provides miscellaneous information that may be helpful to you while you are installing and testing the IT on the DB2 subsystem.

• If you installed the IEFAE version of the sample application (load module IP TIXIVPTS or TIXIVPTE), the application is ready for execution. Exit to the Implementation Toolset Main Menu and select the Application Test Facility option to execute the application. The trancode is MENU.
• If you installed the CICS version of the sample application with DB2 as DBMS (load module IP TIXIVPCE or TIXIVPCI), you must define the program names and trancodes to CICS before you can execute the application. Search through the data set members TIXIVPCE and, TIXIVPCI, in the CEHBSAMP for the literal :PSTEP to find the program names and trancodes for the sample application. The MEMBER is the program name, the DLGTRAN is the dialog flow trancode, and the CLRTRAN is the clear screen trancode. Both types of trancodes must be defined.
• If you installed the IMS BYPASS version of the sample application (load module IP TIXIVPBE or TIXIVPIB), you need to define the PCBs to IMS before you can execute the application.
• If you installed the IMS MAPPED version of the sample application (load module IP TIXIVPIM or TIXIVPME), you need to define the PCBs to IMS and compile the MFS maps before you can execute the application.
• It is possible to install two or more ITs on a single DB2 subsystem. This is not recommended, but if you do decide to do this, you must customize the scripts used to install the IT to ensure the plan name is unique across the DB2 subsystem. This task should be performed by an experienced user. Contact your system administrator for detailed instructions and site specific requirements.
• If you are attempting to verify a second IT installation with the sample load module IP, you must edit the sample load module IP and change all occurrences of the plan name to another unique plan name. If you do not do this, the second verification process fails.