Changing a shared DASD tracker-to-controller connection to an NCF, XCF, or TCP/IP connection

To change a shared DASD tracker connection to an NCF (VTAM®), XCF (SYSPLEX), or TCP/IP one, perform the following steps :
  1. To remove the DASD connection:
    1. In the controller started task procedure:
      1. Remove the EQQEVDnn DD statement pointing to the event data set of the specific tracker.
      2. Remove the DD statement pointing to the Submit/Release data set of the tracker. Not every DASD-connected tracker has a Submit/Release data set, but if one exists, its DDNAME in the controller procedure is the same as the destination listed under the DASD keyword in the ROUTOPTS initialization statement of the controller.
    2. In the controller initialization parameters:
      1. Decrease the value of the OPCOPTS ERDRTASK() keyword by the number of DASD-connected trackers being removed. If there are no DASD-connected trackers, ERDRTASK() is 0.
      2. Remove from the ERDRPARM() keyword the name of the PARMLIB member containing the parameters for the Event Reader task being deleted.
      3. Remove from the DASD keyword in the ROUTOPTS initialization statement the DDNAME of the Submit/Release data set of the tracker.
    3. In the controller ISPF dialogs:
      1. Remove the DDNAME of the Submit/Release data set of the tracker from the workstation destination under dialog option 1.1.2, using the M (modify) row command.
      2. Remove the workstation destination from ROUTOPTS and from the workstation definition.
    4. In the tracker started task procedure, remove the EQQSUDS DD statement.
    5. In the tracker initialization parameters:
      1. In the EWTROPTS statement, set the SUREL() keyword to NO.
      2. In the TRROPTS statement, remove the HOSTCON(DASD) keyword.
  2. To add an NCF connection:
    1. Define the VTAM® LUs for the controller and the tracker. If necessary, create cross-domain definitions. HCL Workload Automation for Z requires that the LU name be the same as the ACBNAME in the APPL. For details, refer to Step 14. Activating the network communication function.
    2. In the controller initialization parameters:
      1. In the OPCOPTS statement, set the NCFTASK() keyword to YES and write the LU name of the controller in the NCFAPPL() keyword.
      2. In the ROUTOPTS statement, write the LU name of the tracker in the SNA() keyword.
    3. In the controller ISPF dialogs, write the LU name of the tracker in the workstation destination under dialog option 1.1.2, using the M (modify) row command.
    4. In the tracker initialization parameters:
      1. In the OPCOPTS statement, set the NCFTASK() keyword to YES and write the LU name of the tracker in the NCFAPPL() keyword.
      2. In the TRROPTS statement, set the HOSTCON() keyword to SNA and write the LU name of the controller in the SNAHOST() keyword.
      3. In the EWTROPTS statement, set the EWSEQNO() keyword to 1.
  3. To add an XCF connection:
    1. In the SYS1.PARMLIB(COUPLEnn) member:
      1. Define the HCL Workload Automation for Z XCF transport class, as described in Updating XCF initialization options.
      2. Define the XCF group that is to enable the controller to communicate with the trackers.
    2. In the controller initialization parameters:
      1. In the XCFOPTS statement, code the GROUP(), MEMBER(), and TAKEOVER() keywords.
      2. In the ROUTOPTS statement, write the XCF MEMBERNAME of the tracker in the XCF() keyword.
    3. In the controller ISPF dialogs, write the XCF MEMBERNAME of the tracker in the workstation destination under dialog option 1.1.2, using the M (modify) row command.
    4. In the tracker initialization parameters:
      1. In the XCFOPTS statement, code the GROUP() and MEMBER() keywords.
      2. In the TRROPTS statement, set the HOSTCON() keyword to XCF.
      3. In the EWTROPTS statement, set the EWSEQNO() keyword to 1.
  4. To add a TCP/IP connection:
    1. Define the IP addresses for the controller and tracker. For details, see Step 15. Using TCP/IP for communication.
    2. In the controller initialization parameters:
      1. In the TCPOPTS statement, set the values to define the details of the local controller. This statement is optional; if you do not specify it, the default values are taken.
      2. In the ROUTOPTS statement, write the TCP/IP destination name and IP address of the remote tracker in the TCPIP keyword.
    3. In the controller ISPF dialogs, write the TCP/IP destination name of the tracker in the workstation destination under dialog option 1.1.2, using the M (modify) row command.
    4. In the tracker initialization parameters:
      1. In the TCPOPTS statement, set the values to define the details of the local tracker or leave the default values.
      2. In the TRROPTS statement, set the HOSTCON() keyword to TCPIP and write the IP address of the controller in the TCPHOSTNAME() keyword.
      3. In the EWTROPTS statement, set the EWSEQNO() keyword to 1.
  5. Stop and restart the controller and tracker for the parmlib changes to take effect, and run the CP extend or the CP replan command to update the current plan with the changed workstation destinations.