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.

Configuring BMC AMI DevX Workbench for Eclipse

This topic provides detailed information about tasks you need to perform to integrate ECC with Workbench for Eclipse.

Task 1: Activating Code Debug support

  1. Update the HCIxx PARMLIB member for BMC AMI DevX Code Debug for TSO, if necessary:
    1. Add the CSPF parameter to specify the fully qualified name for the BMC Shared Profile File data set, as created and populated by the BMC AMI DevX Code Debug for TSO installer.
    2. Add the TSO_* parameters (TSO_SYSNAME, TSO_APPLID, TSO_LOGMODE, and TSO_LPAR) to specify the corresponding system name, APPLID, LOGMODE, and LPAR name values for the four parameters.
    3. Add the APPLID parameters to specify one or more VTAM APPLIDs defined for use by Eclipse.
  2. Update the HCIxx PARMLIB member for BMC AMI DevX Code Debug for CICS, if necessary:
    1. Add the CICS_SYSNAME parameter to specify the CICS region system name.
    2. Add the CICS_SOCK parameter to specify.
    3. Add the CICS_PORT parameter to specify.
    4. Add the CICS_HOST parameter to specify.
  3. Refresh the HCIxx PARMLIB.
  4. Add the BMC AMI DevX Code Debug for TSO Authorized Load Library, SLXTAUTH, to the HCI PROC, HCIPROC.
  5. Restart the HCI.
  6. Install the TSO Logon Procedure.
  7. Verify integration by configuring and running a Code Debug Session.

Task 2: Activating Performance Test/Eclipse support

  1. Modify the HCI PROC (job HCIPROC) to add the fully qualified BMC AMI DevX Performance Test library (SQQFLOAD) in the STEPLIB ??? concatenation.
  2. Modify the HCIxx PARMLIB member to add the HPERPLIB parameter with a value of the fully qualified BMC AMI DevX Performance Test panel library, SQQFPENU.
  3. Restart the HCI.
  4. Use the BMC menu to start the Performance Test/Eclipse perspective.
  5. If the perspective launches and displays audit files, then you have properly activated Performance Test/Eclipse support.

Task 3: Activating Code Coverage/Eclipse support

  1. Modify the SSAS PROC (job CXSSAS) to uncomment the BMC AMI DevX Code Coverage library (SLXVLOAD) in the STEPLIB concatenation and to update with the fully qualified name.
  2. Restart HCI.
  3. Use the BMC menu to start the Code Coverage/Eclipse perspective. Use the Cheat Sheet provided to help you get started.
  4. If the perspective launches and the Coverage Analysis results is displayed from a BMC AMI DevX Code Coverage repository, then you have properly activated Code Coverage/Eclipse support.

Task 4: Activating Code Pipeline support

  1. Modify the HCIxx PARMLIB member by adding the following Code Pipeline Configuration parameters:
    1. ISPW_HOST=ip_addr
      where ip_addr is the IP address, or DNS, of the Code Pipeline server.
    2. ISPW_PORT=port_num
      where port_num is the Code Pipeline server port and must match the value of WZCMXPRT in the Code Pipeline start parms.
    3. ISPW_CTNAME=ct_server_name
      where ct_server_name is the name of the Code Pipeline/CT server that should be used by BMC AMI DevX Workbench for Eclipse clients to access Code Pipeline life cycle data sets. This parameter is required when the CTLOCAL value defined to Code Pipeline does not have access to the life cycle data sets used by the BMC AMI DevX Workbench for Eclipse clients that are connecting through this HCI. This parameter is used in multi-site implementations with a single Code Pipeline server.
  2. Refresh the HCIxx PARMLIB within the CMSC address space.
  3. Restart the HCI.

This task is necessary if you want to activate the BMC AMI DevX Code Pipeline (Code Pipeline) interface in BMC AMI DevX Workbench for Eclipse release 18.2.1 or later. This is also required for Code Pipeline release 17.02 or later with cumulative maintenance applied.

Warning

To connect to multiple Code Pipeline instances from the HCI, the Code Pipeline parameters (ISPW_PORT, ISPW_HOST, and ISPW_CTNAME) must be specified in the HCIxx PARMLIB member after a PORT_CONFIG statement corresponding to that instance. Each Code Pipeline instance requires a separate PORT_CONFIG statement in the HCIxx member (see HCI parameter customization in Configuring-HCI-for-a-new-install)

Task 5: Activating CA-Endevor support

This task is necessary only if you want to activate the CA Endevor interface (the appearance of the Endevor navigation path in BMC AMI DevX Workbench for Eclipse’s Host Explorer perspective).

  1. Modify the HCIxx PARMLIB member to add the ENDEVOR parameter with a value of Y.
  2. Add the Endevor APF-authorized library to the STEPLIB DD in the CSS TP started task (job CXSS0000 in your system PROCLIB).
  3. Restart the HCI.
  4. In the Host Explorer perspective, select a mainframe LPAR and expand to see the paths.
  5. Right-click the Endevor path and select Add Filter.
  6. In the New Endevor Filter dialog box, use the Environment menu to view available environments. The appearance of a list of accessible environments validates that the CA-Endevor interface was properly activated.

Task 6: Activating File-AID/Eclipse support

Perform this task if you want to use the FILE-AID/Eclipse plug-in.

  1. Ensure that you specify a STASK PARM in your HCI PARMLIB member. This is the name of a JCL procedure in a system PROCLIB. A sample procedure named CXSS0000 is supplied. Instructions for setting up the PROCLIB member can be found under Task 2 of Configuring-HCI-for-a-new-install.
  2. In your specified STASK's JCL, un-comment the two lines pointing to the FA CUST LIB and FA DIST LIB. Ensure that the data set names for both libraries are correct for your site.
  3. If you specified FILEAID=NO in your HCI PARMLIB member, change it to YES or remove the line. If you had to change your PARMLIB member, ensure you refresh the member in your CMSC address space.
  4. Restart the HCI.
  5. Verify that the FILE-AID integration was successful by using any FILE-AID plug-in found under the BMC menu.

Where to go from here?

To know more about deploying ECC to other LPARs, see Deploying-ECC-to-another-LPAR.

 

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