Customization procedures

This topic walks you through the following steps for customizing the mainframe portion of Program Analyzer. This customization establishes the link between components that communicate with the workstation and the MVS host.

• Step 1. Execute Customization Manager
• Step 2. Define Dataset Names
• Step 3. Specify Options
• Step 4. Define Variables for TP Definitions
• Step 5. Perform Customization Tasks
• Step 6. Establish Security Protections
• Step 7. Set Up HCI Security

The customization process is handled by Customization Manager, an automated ISPF-like application that prompts you to enter the site-specific information you collected and controls running a series of batch jobs that complete the customization process.

Step 1. Execute Customization Manager

Due to naming conflicts with the DevEnterprise customization dialog, the Program Analyzer customization dialog has been packed in XMIT format as member XAXMIT in the SLCXCNTL library. Do a TSO RECEIVE command on <smpehlq>.SLCXCNTL(XAXMIT) to a new PDS named <yourhlq>.XAINST.

1. Execute the CLIST $XASETUP from the install data set (created when you did the TSO RECEIVE of XAXMIT above) by entering the following in an ISPF/PDF COMMAND field:
   
   TSO EX '<yourhlq>.XAINST($XASETUP)'
   
   The SOFTWARE LICENSE AGREEMENT screen appears.
2. Read the agreement and type 1 to accept the agreement or 2 to reject the agreement. Press Enter. If you accept the agreement, the Welcome screen appears.
3. Select option 1 to begin customization.

Step 2. Define data set names

1. Select option 1 and press Enter on the SET UP screen to define the names of data sets required for this customization. The DATASET NAMES screen appears.
2. Select option 1 and press Enter to display the PRODUCT DATASETS screen.
3. Confirm the correct entries for all data sets under Dataset Name. These entries match the Compuware Program Analyzer dataset names table, which are based on the SMP/E data set high-level qualifier you entered when specifying SMP/E high-level qualifiers as described in the Compuware Installer Mainframe Products SMP/E Installation Guide. Refer to Using the CHANGE Command to easily perform search-and-replace operations on character strings.
4. Press F3 to save your changes and return to the DATASET NAMES screen.
5. From the DATASET NAMES screen, select option 2 and press Enter to display the ADDITIONAL LIBRARIES screen.

6. Enter the data set names to match your existing site standards, making sure to scroll down and confirm the correct entries for all data sets. Enter the fully qualified data set names for the LE370 Runtime Library, IEFJOBS Library, and System Proclib installed at your site.

   If any of the listed components are not installed at your site, leave the space in the Customization Manager dialog box blank.

   The library names you specify during the Program Analyzer customization must match those used in the XPPTCPIP TP JCL member. If library names change after the customization, make corresponding changes to the JCL.

7. Press F3 until you reach the SET UP screen.

Step 3. Specify options

1. In this step, you will specify the customization parameters. The table is populated with the default values delivered with the product. If you are upgrading from a prior release, make sure that the following options are different from the ones specified in the previous installation.

2. Select option 2 and press Enter on the SET UP screen. The OPTIONS screen, which is several pages long, appears. Verify and/or update the values, making sure to scroll down and confirm the correct entries for all values. These entries match the Installation options table.

   For information on a specific field, type an H in the CMD field to display help. Whenever you are scrolling through a list of options, make sure that SCROLL is not set to MAX. Specify either CSR, HALF or PAGE to ensure that you do not skip over list items.

3. If you chose to set up your started task TPs with master JCL using the IEFJOBS DD concatenation, do the following:
4. Verify that both STTP and STTPMJCL customization option variables are set to YES for TPs to run with master JCL.

5. Verify that the data set name associated with DD IEFJOBS in the master scheduler JCL data set (commonly known as the MSTJCLxx member of SYS1.PARMLIB) is specified in the ADDITIONAL LIBRARIES screen. Refer to the ECC Shared Services and System Libraries dataset names table. Customization Manager creates members in this data set that contain tailored job cards and an execute card to support each started task TP.

   Ensure that the HCI Authorized Library is APF-authorized and is available on all MVS images. This library must be APF-authorized on every MVS, not just on the MVS where the HCI will run.

6. Press F3 to save your changes and return to the SET UP screen.

Step 4. Define variables for TP definitions

In this step, you will define the variables for the Transaction Program (TP) definitions you will use with Program Analyzer. This includes the TP names and member names for the TP JCL and the TP types.

1. Select option 3 and press Enter on the SET UP screen. The TP DEFINITIONS screen appears.
2. Review the table and update the values where appropriate. TPs are provided as part of the installation. These entries match the TP definitions table. If you are upgrading from a prior release, make sure that the TP NAME is different from the ones specified in the previous installation. Make sure to change the PARMLIB MEMBER name from the default—HCITCPIP—to the new name specific to the new release of the product. This ensures that the existing HCITCPIP will not be overwritten when a new started task is copied into your system’s PROCLIB.
3. Press F3 to save your changes and return to the SET UP screen.

Step 5. Perform Customization Tasks

The SET UP screen's Option 4 - Installation contains a list of tasks that must be selected and processed sequentially to install Program Analyzer.

Some tasks generate a batch job and then invoke an ISPF/PDF Edit session for the job. Review this JCL and submit the job, then review the job output before moving on to the next task.

For each task, use the S line command to generate JCL from the values entered in Options 1-4 on the SET UP screen. When you use the S or E line command, a standard ISPF/PDF Edit screen appears with notes and comments that explain what to do next. It is imperative that you read the internal notes and comments for each task to understand the steps that are taking place during the installation. Most of the JCL or objects should not require any manual modification.

If you are upgrading from a prior release, after you have performed the following installation tasks, the new TP is independent and separate from the TPs currently running at your site.

1. Select option 4 and press Enter from the SET UP screen to display the CUSTOMIZATION screen.
2. Enter S in the Cmd field next to Task 1. This task generates a report from the information you entered. This information will be used to configure the workstations to connect with the host component of Program Analyzer. It also contains a report describing the definitions needed in the HCI PARMLIB.

3. Enter S in the Cmd field next to Task 2.

   This task will run either as a batch job or as a started task depending on how you set the STTP installation variable earlier (see here). Compuware strongly recommends that you run the TPs as a batch job during the Program Analyzer installation to make it easier to verify that they execute properly, and then convert them to run as a started task (see Step 6). This will eliminate contention for JES initiators and prevent getting 1011 error messages on a workstation when starting TPs. Before you can test your TPs, the HCI must be active with the Program Analyzer definitions. Task 5 will generate a report with the HCI definitions needed for Program Analyzer.

4. Select the displayed TP JCL member and submit it and ensure that at least one member is executing the program XWXML. The XPPTCPIP TP terminates with a completion code of 56 because it was started manually rather than by HCI. Ignore this code. If your installation is correct, the results should be that the TPs execute and go to a waiting status.

   The TPs must be submitted on the same MVS image that the HCI is running on. If you have JES/3 installed on your system, make sure the CLASS parm directs the job to the same MVS image that the HCI is running on.

5. Verify that the TP started and then cancel the TPs.
6. If you ran the TPs as batch jobs, Compuware recommends, now that you have verified that they can execute without errors, that you convert them to started tasks. To do this, do the following:
   • Press PF3 until you reach the SETUP screen.
   • Select option 2 and press Enter.
   • On the OPTIONS screen, change the value of STTP (the install option variable for TPS) to YES.
   • Press PF3 to return to the SETUP screen and select option 4.
   • On the CUSTOMIZATION screen, enter S in the Cmd field next to Task 2 and rerun it.
     Running the HCI and TPs as a started task will eliminate contention for JES initiators and prevent getting 1011 error messages on a workstation when starting TPs

7. Enter S in the Cmd field next to Task 3. This task copies the JCL members that were generated and tested in Task 2 to the PROCLIB data set if you set up the HCI to run as a started task (or to the PARMLIB data set if you set up to run as a batch job).

   For the JCL to successfully copy your started tasks to the system's PROCLIB, the PROCLIB name must be specified on the DATASET NAMES screen and the STTP install options variable must be set to YES. If you choose to run transaction programs as started tasks, an extra option is available to run these started tasks with master JCL using the IEFJOBS DD concatenation. Refer to Step 3.

The mainframe installation is now complete. To exit the Customization Manager, select X on the WELCOME screen and press Enter.

Step 6. Establish security protections

If your site uses a security package, assign the following protections for any of the data sets that were created during the installation.

System Security for the HCI

Step 7. Set up HCI security

If you are running HCI as a started task, the user ID associated with this task must have READ authority to the ECC data sets.

To use HCI with TCP/IP, Open Edition MVS segment (OMVS) access also needs to be defined.

For more information about HCI security considerations, refer to System Security for the HCI.

TP performance considerations

Compuware suggests assigning TPs to a performance group above BATCH but below CICS, VTAM, and JES.

Summary

This completes the base installation of the Program Analyzer components that communicate with the host.

You can now install, set up, and verify the Program Analyzer workstation components. Refer to the help for step-by-step procedures for installing and setting up the product.

Using the CHANGE command

Several screens within Customization Manager provide a CHANGE command that allows you to perform a search-and-replace operation on character strings. For example, if you enter CPWR.MLXW530 in the FROM field and CPWR.MLXW160 in the TO field, all data set names in the table are changed accordingly.

If you are upgrading from a prior release, change all data set names to be different from the existing data set names, thus ensuring that the new release is installed in different data sets.