Rational Developer for System z, Version 7.6

Connecting to CARMA

CARMA requires a connection to a CARMA host in order to retrieve SCM information from the host. CARMA uses the connection services of the Rational Developer for System z Remote System Explorer (RSE) to connect to the host. To create a new CARMA connection, follow these steps:

  1. In the CARMA Repositories view do one of the following:
    • Click the New Connection button (screen capture of the New Connection button).
    • Right-click inside the view and click New Connection.

    The New CARMA Connection wizard opens.

    Figure 1. New CARMA connection wizard
    First panel of the New CARMA Connection dialog
  2. Choose one of the options from the list and click Next.
  3. If you chose to create a new CARMA connection from an existing RSE connection the following dialog opens:
    Figure 2. New CARMA connection wizard
    Second panel of the New CARMA Connection dialog

    Choose the RSE connection you want to create a CARMA connection from using the drop-down list and provide a name for the new CARMA connection. By default, the name of the existing RSE connection is used for the name of the CARMA connection. This is the label that will be used for the connection in the CARMA repositories view. Skip to step 8.

  4. If you chose to create a new RSE and CARMA connection, the New Remote z/OS® System Connection wizard opens.

    Note: If this is the first time that you have attempted to create a connection in RSE, you will not see the dialog below yet, but will instead be prompted to create a profile before you can create the new connection.

    Figure 3. New connection dialog
    First panel of the New Remote z/OS System Connection wizard
  5. Complete the following fields in this dialog:
    Parent profile
    The profile named after your workstation appears by default. To choose a different profile, select a predefined profile from the drop-down list. After you create the connection, you can share this profile to allow other users to have this connection in their RSE perspective.
    Connection name
    A unique name to identify your connection in the Remote Systems view. For example, Development System or Test System. The label that you assign to this connection will help you to differentiate between multiple connections to the same type of remote system.
    Host name
    The hostname or IP address of the z/OS system that your RSE server is installed on.
    Description
    A short description of the z/OS system that you want to connect to, for example, Development System or Test System. The description that you assign to this remote system will help you to differentiate between multiple remote systems of the same type.
    Verify host name (optional)
    To verify that the hostname or IP address in the Host name field is valid, select the Verify host name check box.
  6. Do one of the following:
    • If you don't need to configure any JES or USS files subsystem properties, skip to step 8.
    • Click Next to proceed to the JES SubSystem Properties page.
      Figure 4. JES subsystem properties dialog
      JES subsystem panel of the New Remote z/OS System Connection wizard

      In the JES tab:

      1. In the JES Job Monitor Port field, type the port on which the Remote Job Monitor is listening.
      2. In the Max Number of Lines to Download field, type the number of lines to download before prompting you to specify if you want to download all of the lines in the data set.
  7. Do one of the following:
    • If you don't need to configure any USS files subsystem properties, skip to step 8.
    • Click Next to proceed to the USS Files SubSystem Properties page.
      Figure 5. USS files subsystem properties dialog
      USS files subsystem properties of the New Remote z/OS System Connection wizard

      In the Server Launcher Settings tab, specify the default method for launching the remote server:

      • To automatically start the RSE host server using a server daemon:
        1. Click the Remote daemon radio button.

          Note: You must start the server daemon using the root user ID. If you do not start the server using the root user ID, it cannot authenticate users who are trying to connect to the server.

        2. In the Daemon Port field, type the port number that is used by the server daemon on the remote host. By default, port 4035 appears.
      • To automatically start the RSE host server using an REXEC command:
        1. Click the REXEC radio button.
        2. In the Path to installed server on host field, type the path where the RSE host server is installed on the remote host. You can specify a path that is relative to the directory where you run the REXEC command or the full path to the location where the server is installed. For example, dstore or /usr/bin/dstore.
        3. In the Server launch command field, type the name of the script file to run when you use the REXEC command to start the RSE host server. By default, server.zseries appears; this is the sample script file that is shipped with IBM® TPF Toolkit for WebSphere® Studio to start the RSE host server.
        4. In the Port field, type the port number that is used by the REXEC daemon on the remote host. By default, port 512 appears.
      • To connect to an RSE host server that you start manually:
        1. Click the Connect to running server radio button. If your remote system is not configured to use REXEC to start the RSE host server, this option allows you to connect to an RSE host server that you start manually.
          Note: When you start the RSE host server manually on the remote host, you can configure it to receive connection requests at a specified port or to use the next available port on the system. The port number used by the server is displayed when you start the server. After you start the server, you must specify that port number in the Subsystem properties page before you can connect. To access the Subsystem properties page:
          1. Switch to the RSE perspective.
          2. In the Remote Systems view, double-click the z/OS connection to expand it and reveal the USS Files subsystem.
          3. Right-click the USS Files node and select Properties from the pop-up menu to open the Properties for USS Files dialog box.
          4. In the left navigation pane, click Subsystem to open the Subsystem properties page.
  8. Click Finish to create the new CARMA connection and add it to the CARMA Repositories view.
  9. To activate the connection, do one of the following:
    • Right-click on the connection and select the Connect menu item.
    • Alternatively, you can activate a connection by expanding the connection by clicking the + next to the connection name. Note that this method will only work the first time you are connecting to this CARMA host. Use the previous method to explicitly connect to the CARMA host for subsequent connection attempts.
    Note: Attempting to perform any action on the elements under a CARMA connection will automatically activate the connection.
  10. In the Enter Password dialog, type a valid user name and password and click OK. A list of repository access managers (RAMs) appears under the CARMA host in the CARMA Repositories view.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)