Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.
Space announcement To view the latest version of the product documentation, select the version from the Product version menu above the navigation pane.

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 DevEnterprise.

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.

Important

  • S Line Command vs. E Line Command for Generating and Editing JCL
    To generate the JCL for the task, you must use the S line command before you can submit the associated job. If you make changes to the JCL immediately before submitting, your changes will be lost if you later attempt to resubmit the job after using the S line command (that is, the JCL is regenerated). You can resubmit the job using the most recent version of the JCL by using the E line command.
  • Before installing, make sure the library you designated for the HCI Authorized library is APF-authorized. You will receive a 047 abend from Step 8 if the library is not properly authorized.


  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 DevEnterprise. It also contains a report describing the definitions needed in the HCI PARMLIB. 

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

    Warning

    This task will run either as a batch job or as a started task depending on how you set the STTP installation variable earlier. We strongly recommends that you run the TPs as a batch job during the DevEnterprise 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 DevEnterprise definitions. Task 5 will generate a report with the HCI definitions needed for DevEnterprise.

  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.

    Important

    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, we recommend, 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)


Warning

For the JCL to successfully copy your started tasks to the system's PROCLIB, the PROCLIB name must be specified on the DATA SET 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. See to the step detailing how to set up started task TPs with master JCL.

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

Important

BMC Software provides exits X2MARXIT and X2AARXIT. These exits can be modified to alter source names of collected members. If the exits were modified and used in the previous release of DevEnterprise, the modified exits must be made available to the new release of DevEnterprise. If the modified exits were linked into the DevEnterprise load library, the exits should be copied into the newly installed load library. If the exits were linked into a private library that was ahead of the DevEnterprise load library concatenation insure the new load library concatenation includes that private library. See Metadata Analyzer Exits for more information on Metadata Analyzer exits.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*