Appendix II - Sample: TMDEMO

A sample called TMDEMO is provided with the ART Test Manager. It’s a small mainframe application that contains CICS, IMS, and Batch components. The step-by-step tutorial below is intended to help users get familiar with all the key functions of the ART Test Manager based on this sample.

•	Application Description

•	Migrating and Deploying TMDEMO Using ART Workbench

•	Setting Up ART Test Manager Project

•	Configuring Test Environment

•	Testing CICS 3270 Screens

•	Testing IMS 3270 Screens

•	Testing Batch Jobs

•	Using Dashboard

•	Using Audit Trail

Application Description

TMDEMO application is a combination of a simple banking application using IMS online transactions and a batch program coupled with a set of CICS screens for maintaining customer contact information. The online transactions and batch jobs in this sample that map to CICS, IMS, and Batch test cases. Some test cases load data from file into database; others update or delete data in database. This sample can show you some basic operations about TM.

Databases and Files

The test cases in this sample access some files and Oracle database migrated from IMS DB.

Application Components

CICS Components

There are six CICS programs in this demo.

 

Table 14‑1 CICS Programs

Name	Description
RSSBT000	Customer maintenance entry program.
RSSBT001	Customer data inquiry program.
RSSBT002	Customer data maintenance program (new/update and delete customer).
RSSBT003	Customer list program.
TOLOSVR	DPL program to change input to lowercase.
TOUPSVR	DPL program to change input to uppercase.

IMS Components

There are seven IMS test units in TMDEMO, six IMS MPP online transactions and one cases and one BMP program. Their functions are listed in following table.

 

Table 14‑2 IMS Program Functions

Case Name	Type	Function
BANKCLNT	IMS MPP	It’s the entry for other transaction (including DEPOSIT, WITHDRAW, TRANSFER, INQUIRY)
DEPOSIT	IMS MPP	Used to deposit money to an existing account
WITHDRAW	IMS MPP	Used to withdraw money from an existing account
TRANSFER	IMS MPP	Used to transfer money from one existing account to another
INQUIRY	IMS MPP	Used to inquiry the balance of an existing account
BANKMGMT	IMS MPP	Used to open an account and close an account
INSTERET	IMS BMP	Used to add interest for all the existing account

Batch Components

There are three Batch jobs in the sample. All the batch jobs run COBOL programs to insert or update data in database or to generate a report file from the database.

 

Table 14‑3 Batch Jobs

Case Name	Program Called	Description
LODCUST.jcl	RSSBBB00	Insert data read from file into database (Table ODCSF0).
UPDCUST.jcl	RSSBBB02	Update data to database.
PRTCUST.jcl	RSSBBB01	Fetch data in database.

Migrating and Deploying TMDEMO Using ART Workbench

Before the application can be tested with the ART Test Manager, it must be migrated from the mainframe version using Tuxedo ART Workbench so that it can run in Tuxedo ART environment. The following briefly explains how to use the eclipse plug-in to execute the ART Workbench migration life-cycle. For more information refer to Tuxedo ART Workbench User Guide.

1.	Use menu “File->New->Project” in Eclipse to create a new project, select “Tuxedo ART Project” as project type in the list.

2.	Specify the installation path of Workbench.

3.	Specify the application source directory in the following page. This is the location ./TMDEMO/source.

4.	After selecting the target database and compiler type, you can click “Finish” button in the right corner, then the project is created.

5.	Use ART pull down menu on Eclipse tool bar to run Import and Prepare lifecycle steps. Keep all the default options.

6.	Use ART pull down menu to bring up Configure Scope dialog: ART->Analyze-> Configure Scope, then select the corresponding Type for each directory as shown below:

 

Table 14‑4 Select Type for Each Directory

Directory Name	Type	Content
IMS_DBD	IMS-DBD	IMS DBDGEN extract
IMS_PSB	IMS-PSB	IMS PSBGEN extract
IMS_APPL	IMS_APPL	IMS APPLCTN macros
IMS_MFS	IMS_MFS	MFS IMS screen maps
JCL	JCL	Batch JCL
CICS	Cobol-TPR	COBOL/CICS programs
COPY	Cobol-Library	Copybooks
MAP	BMS	BMS CICS screen maps
IMS_COPY	Cobol-Library	Copybooks
IMS-COBOL	Cobol-Batch	COBOL/IMS
DDL	SQL-Script	DB2 DDL
BATCH	COBOL-Batch	Batch COBOL programs
RDO	RDO	CICS CSD extract

When all Types have been correctly selected click “Select All” button to change “Process” column value of all the directories to “YES”, and then click “Finish”. This will set up the Workbench configuration appropriately for each of the directories.

7.	Create or copy two parameter files for File Converter. These can be copied from <TMDEMO sample direcotry>/param/file to the <ART WB TMDEMO Project directory>/param/file in order to generate the file converter artifacts for the sample.

8.	Set default Oracle Database schema to use for the Oracle table and other objects as follows. Open project Properties by right clicking TMDEMO project name in Workbench Navigator and selecting “Properties” at the bottom of the menu as following:

Select “ART Workbench -> Global-> SQL” and input “PJ01DB2” into “Default SQL Schema” text to specify the schema name, then click “Apply->OK” finish this step.

9.

Run ART Workbench Cataloger using ART drop down menu on Eclipse toolbar: “ART->Analyze -> Catalog”. To check whether the catalog process finished successfully check whether there are any ERROR-level messages in the Console view or open “Catalog Reports” view and check Anomalies report shown below to ensure there are no “ERROR” or “FATAL” severity messages (WARNING messages are expected) as well as any ERROR messages in any other report tabs.

10.

Open ART Workbench Converters Wizard using ART drop down menu on Eclipse toolbar: ART->Convert. Click “Select All” button to check all items, and then click “Finish”. To verify that converter process finished successfully, check for any ERROR level messages in “Console” view or open “Tracking” view and, check the “Converted” column under “Code summary” tab to ensure all JCL, CICS, IMS, and Batch components show 100% converted as shown in the figure below.

11.	Enter Configuration wizard: “ART->Configure”. Use local machine configuration as default or add remote machine configurations.

a.	Check “Enable Batch Runtime Configuration”, “Enable CICS Runtime Configuration”, “Enable IMS Runtime Configuration”, “Enable ART Test Manager”

b.	Open each tab and enter the relevant configuration information. Note that under IMS one of the input fields is an IPCKEY for ART Test Manager agent. This IPCKEY must be unique in the system.

After all the parameters are configured, click “Finish”.

12.	With configurations defined and makefiles generated build the application executables by using ART Workbench Build wizard: “ART->Build”. Click “Select All” button to check all the items, then click “Finish” to launch the build steps in the sequence shown in the figure below.

To verify that build processes finished successfully, check the “Console” for any ERROR level messages or use “Tracking” view to check the “Compiled” column value under “Code summary” tab. It should show 100% results for CICS, IMS, and Batch programs. Value for JCL will be blank as JCL is not compiled.

13.

To deploy the migrated, configured, and built application select “ART->Deploy” wizard. Enable “Batch”, “CICS” and ”IMS” in target selection area, then click “Pack Target” to package application components and configuration artifacts for each runtime. After pack step has finished, click “Deploy Application” to deploy the application packages to the target APPDIR directory specified in the Configure wizard. Then click “Finish”. To verify that this step has finished successfully, check the log in “Console” view for any ERROR level messages or open “Tracking” view to check “Deployed” column value under “Code summary” tab. It should show 100% of the components have been deployed as shown in the figure below.

14.

Before starting Tuxedo domains for each runtime, Setup Runtimes function must be run to prepare the domain dependencies. This can be done from ART->Deploy->Setup Runtimes wizard; however, if this project will be used by the ART Test Manager, this step is optional as ART Test Manager will automatically perform these functions before starting the domains. To execute this step in the ART Workbench plugin open the wizard: “ART->Deploy->Setup Runtime”, check the three checkboxes: “Setup Batch runtime environment”, “Setup CICS runtime environment”, “Setup IMS runtime environment”, then click “Finish”. To verify the setup status, check the log in “Console” view.

15.	To provide the data files required by the application, open the Reload File Data wizard as follows: ART->Deploy->Reload File Data. Specify <TMDEMO directory>/data_source as VSAM/QSAM source location as shown in the figure below.

Specify the Data Source Files as shown in the following table:

 

Table 14‑5 Data Source File

File Schema	File Name	Data Source File
TMDEMO	PJ01AAA.S2.QSAM.CUSTOM.UPDATE	PJ01AAA.S2.QSAM.CUSTOM.UPDATE
TMDEMO	PJ01AAA.S2.QSAM.CUSTOM	PJ01AAA.S2.QSAM.CUSTOM

Input the deploy target location, and click “Finish”. To verify that file conversion and reload were successful check the log in “Console” view or open “Tracking” view and check status in Reloaded column under “Data summary” tab.

16.	To reload the database table required by the application, open the Reload DB2 Data Data wizard as follows: ART->Deploy->Reload DB2 Data. Specify <TMDEMO directory>/data_source as data source location and specify “DB2 Data File” as shown in the following table:

 

Table 14‑6 DB2 Data File

DB Schema	Table Name	DB2 Data File
PJ01DB2	ODCSF0	PJ01DB2.ODCSF0.DATA

Click “Finish” to perform data transcoding and reload Oracle table. To verify that database reload finished successfully check the log in “Console” view, which should contain the messages as shown in the figure below.

The TMDEMO application has been migrated, configured, built, and deployed and its data dependencies have been similarly converted and reloaded. It is ready to run and can be tested using ART Test Manager as described in the next section of this tutorial.

Setting Up ART Test Manager Project

Once ART Test Manager has been installed and configured, start Tomcat as described in 2.2.2 Configuring and Starting ART Test Manager. Specify hostname:port/arttm URL in a web browser address bar to get to the login page, enter username “admin” and admin’s password as specified during ART Test Manager installation, and click Login button. Once logged in, proceed with the next steps as admin user or use the pull down menu under admin in the upper right corner to enter User Management and create a new, regular user. Continue the tutorial with the steps below.

To create an ART Test Manager project, click the “Create project” button in Context Path Bar and enter the required information.

•	“Project Name”: A name to identify your project.

•	“Deploy Path”: The path of your migrated application, it’s the APPDIR where ART Workbench deployed the migrated TMDEMO application.

•	“Project Path”: The path where ART Test Manager will maintain the project information. It will contain content from the APPDIR and metadata created by ART Test Manger.

If Workbench APPDIR is not on the same machine where ART Test Manger is installed and running, check “Remote Project” check-box and provide required machine and connection information as shown in the figure below.

After you provide necessary information, and click “Create” button, a new project would be created. ART Test Manger will automatically scan the deployment APPDIR and create default test groups including all the discovered test cases. These groups are always named “BATCH_RT” for BATCH cases, “CICS_RT” for CICS cases and “IMS_RT” for IMS cases. For “Batch_RT”, the batch test cases represent the jobs found under JCL directory. For “CICS_RT”, the CICS 3270 test cases represent the transactions listed in the configuration file transactions.desc and the CICS DPL test cases represent the DPL programs listed in the configuration file programs.desc. For “IMS_RT”, the IMS MPP and BMP test cases represent the online and batch programs listed in the configuration files imstran.desc and imsapp.desc.

After creating the TMDEMO project, click on the project in the left navigation tree to open the project context consisting of the three test groups in the main operations pane. Notice the Case Count column shows the number of test cases in each group – these are the cases automatically discovered and imported from the APPDIR when the project was created.

Configuring Test Environment

Once the project is created in ART Test Manager, the test environment has been configured.

Testing CICS 3270 Screens

As described in the User Guide, to test CICS 3270 screen, first run the transactions against the mainframe and capture the baseline using tn3270 recorder.

Capturing and Uploading Baseline

Follow the guidelines in Appendix I of this User Guide on how to configure and use the TN3270 Recorder. Afterwards, upload the captured baseline “.tgz” files using the “Upload” dialog of each CICS 3270 test case as shown in the figure below.

Executing Test Cases and Comparing Results

After uploading the baseline select one or more CICS 3270 test cases and click the “Run” button to execute selected cases.

The “Status” column indicates if the test case has failed or passed. For detailed result click the icon in the “Result” column to see any detailed differences if they exist.

For RSSBT00 case, the difference is on one field located at row 1 column 70 of the second screen. The mainframe value “08-03-17” doesn’t match ART value “24-03-17”. This is in fact a date field that contains the current execution date. It is normal for this field to not match unless the baseline from the mainframe execution was done on the same date and ART execution. Check the check-box to the left of the field and click “Add to filter file” button to filter this field from the any future comparison. Once this case is re-run, the will be no other differences identified in the datastream and the case will pass.

Testing IMS 3270 Screens

To run IMS cases perform the following steps to finish preparing the IMS environment before starting the Tuxedo domain for IMS MPP and BMP regions.

1.	cd to <TMDEMO Directory>/ims_prepare directory, edit the setenv.sh corresponding to the compiler used, to update the values of IMSDIR, COBDIR, ORACE_HOME, ORACLE_USER, and then source this setenv script.

2.

Execute script run.sh under <TMDEMO Directory>/ims_prepare to replace libdlidb.so, compile DLI-to-Oracle Data Access Layer programs, and reload IMS DB data into Oracle schema. To verify that database reload succeeded, check that the following output is displayed showing contents of two Oracle tables reloaded from IMS DB data.

3.	In ART Test Manager project context open “Configuration” dialog for IMS group by clicking on the icon under Configure column and click “Env Setting” tab. In this tab, append the following env variable settings at the end and click “Save” button in lower right:

export USER_GNT_PATH=<TMDEMO Directory>/ims_prepare/sourceprogram

export $coblib=${USER_GNT_PATH}:${!coblib}

This completes the prerequisites for running TMDEMO IMS test cases.

Capturing and Uploading Baseline

As in CICS 3270 cases, before running IMS MPP cases prepare and upload the baseline from mainframe execution. In IMS group context displaying all IMS test cases, click the “Configuration” column icon for BANKCLNT case. In this Configuration dialog, click “tn3270rcd” tab and specify the required values in the “Mainframe Host Name” and “Mainframe Host Port” fields. Click “Test Connection” button to verify the connection. Once connection has been verified, click “Start tn3270rcd” button to start the recorder and note the hostname:gwPort in tn3270rcd’s message.

Start a tn3270 terminal emulator session and connect to hostname:gwPort specified in tn3270rcd’s message. Navigate to the IMS BANKCLNT application, press PA1 to start recorder, and perform normal sequence of interactions with the application. When finished, press PA1 to end the recorder and save the datastream baseline.

Back in ART Test Manager, click “Kill tn3270rcd” and “Collect Baseline” buttons to terminate the recorder and upload the baseline for the BANKCLNT test case.

Executing Test Cases and Comparing Results

To run the IMS MPP case, check BANKCLNT and click the “Run” button. The uploaded baseline will be used to drive the interaction with BANKCLNT transaction in ART IMS environment. Click the Result column icon to check the execution results, starting with the execution log displayed under “Console” tab, which should look similar to the log sample in the figure below.

Click “Screen Diff” tab to check the data stream comparison. Under “Diffs” tab the two fields with differences are indicated as shown in the figure below.

The two fields contain timestamp values, which would most likely be different between the captured mainframe baseline and ART IMS execution. To filter these fields out of any future comparison, select them using checkboxes to the left and click “Add to filter file”.

Click on the “Screens” tab to check the side-by-side screen views.

Testing Batch Jobs

There are three jobs in the sample and they appear as three batch test cases in BATHC_RT group as shown in the figure below.

Executing Test Cases and Comparing Results

To execute a test case, first click “Startup Domain”. Once the domain is up select the jobs to test using checkboxes on the left and click “Run” button to launch them. The output will be displayed in the console view below.

Return Code Comparison

The default result checking for batch test cases is to check the return code of the job. For a native JCL job, the return code 0 is taken as test passed; any other value means it failed. For a KSH job, C000 return code is taken as passed, any other value means it failed.

Setting Up and Using File Compare

File compare option is used to compare files in ART Batch with datasets on mainframe after the job has been executed. When this option is enabled and FTP connection has been set up and verified, ART Test Manager will submit the job on the mainframe and download the referenced data from mainframe to Linux. After transcoding and reloading data, files will be compared.

In order to ensure the job runs successfully on the mainframe verify that all the PROCs and programs referenced by the job can be found on the mainframe, that all required datasets are available, and that the state of the database is as expected by the job.

File compare option is disabled by default. This option can be enabled in the Batch configuration dialog. Click “Config” button on the group panel to access the configuration dialog.

Choose “Enable File Comparison” and input the mainframe information including host name, ftp port, user name and password. Try ftp connection by clicking “Test FTP Connection” button. Then click “Save” button.

After configuration select and “Run” this test case then click result icon to view results. In the results dialog click “File Compare” tab to check the result of file comparison.

The left pane lists the file referenced by the job. Click the file to see any differences from the comparison.

Setting Up and Using DB Compare

When batch test cases update the database, DB compare option can be used to compare DB operations between mainframe execution of the job updating DB2 and ART execution updating Oracle Database. This also involved submitting the job on the mainframe using FTP connection, so it also requires the mainframe environment to be set up correctly in order to be able to run the job.

DB compare option is disabled by default but it can be enabled by the configuration dialog for Batch group. Click “Config” button on the group panel. (Refer to Configure Mainframe Connection for the dialog details.) Select “Enable DB Operation Comparison”, and input the mainframe information including host name, ftp port, user name and password, then test ftp connection by clicking “Test FTP Connection” button. Then input DB2 information including DB2 home, DB2 name, DB2 port, DB2 user name and password and test DB2 connection with “Test DB2 Connection” button. When both FTP and DB2 connections are successful, click “Save” button to save the configuration.

After configuration select LODCUST batch case and click “Run” button to execute it. After execution click Result column icon to open the results dialog and click “DB Compare” tab to see the comparison of DB operations between DB2 on the mainframe and Oracle Database.

As illustrated in the figure above, the INS (ert) operations are shown in the left pane. Clicking on any of them shows the BEFORE and AFTER values in the table for both Oracle and DB2, which in these case match 100%.

Using Dashboard

Click “Dashboard” button on the project, group, or test plan panel to see case execution report of the TMDEMO project. Total/passed/failed number and passed/failed percentages will be listed in table format for each case type.

Use the filter search boxes on the top of the table to filter the dashboard to a required subset based on group name, test plan name, or test case types.

Using Audit Trail

Click “Audit” in the drop down menu in upper right corner to see and audit report of all operations performed on project TMDEMO. Starting and ending timestamp, userid, action, target object, action details, status, and if failed, reason for failure will be shown in the table.

Filters above the table can be used to restrict the audit report to specific date/time range, actions, or users.