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 :
- To remove the DASD connection:
- In the controller started
task procedure:
- Remove the
EQQEVDnn
DD statement pointing to the event data set of the specific tracker. - 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 theROUTOPTS
initialization statement of the controller.
- Remove the
- In the controller initialization parameters:
- 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. - Remove
from the
ERDRPARM()
keyword the name of thePARMLIB
member containing the parameters for the Event Reader task being deleted. - Remove from the
DASD
keyword in theROUTOPTS
initialization statement the DDNAME of the Submit/Release data set of the tracker.
- Decrease the value of the
- In the controller ISPF dialogs:
- 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. - Remove the workstation
destination from
ROUTOPTS
and from the workstation definition.
- Remove the DDNAME
of the Submit/Release data set of the tracker
from the workstation destination under dialog option 1.1.2, using
the
- In the tracker
started task procedure, remove the
EQQSUDS
DD statement. - In the tracker initialization parameters:
- In the
EWTROPTS
statement, set theSUREL()
keyword toNO
. - In
the
TRROPTS
statement, remove theHOSTCON(DASD)
keyword.
- In the
- In the controller started
task procedure:
- To add an NCF connection:
- 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. - In the controller initialization parameters:
- In the
OPCOPTS
statement, set theNCFTASK()
keyword toYES
and write the LU name of the controller in theNCFAPPL()
keyword. - In the
ROUTOPTS
statement, write the LU name of the tracker in theSNA()
keyword.
- In the
- 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. - In the tracker initialization parameters:
- In
the
OPCOPTS
statement, set theNCFTASK()
keyword toYES
and write the LU name of the tracker in theNCFAPPL()
keyword. - In the
TRROPTS
statement, set theHOSTCON()
keyword toSNA
and write the LU name of the controller in theSNAHOST()
keyword. - In
the
EWTROPTS
statement, set theEWSEQNO()
keyword to 1.
- In
the
- 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
- To add an XCF connection:
- In the
SYS1.PARMLIB(COUPLEnn)
member:- Define the HCL Workload Automation for Z XCF transport class, as described in Updating XCF initialization options.
- Define the XCF group that is to enable the controller to communicate with the trackers.
- In the controller initialization
parameters:
- In the
XCFOPTS
statement, code theGROUP()
,MEMBER()
, andTAKEOVER()
keywords. - In the
ROUTOPTS
statement, write theXCF MEMBERNAME
of the tracker in theXCF()
keyword.
- In the
- In the controller ISPF dialogs, write the
XCF MEMBERNAME
of the tracker in the workstation destination under dialog option 1.1.2, using theM
(modify) row command. - In the
tracker initialization parameters:
- In the
XCFOPTS
statement, code theGROUP()
andMEMBER()
keywords. - In the
TRROPTS
statement, set theHOSTCON()
keyword toXCF
. - In the
EWTROPTS
statement, set theEWSEQNO()
keyword to 1.
- In the
- In the
- To add a TCP/IP connection:
- Define the IP addresses for the controller and tracker. For details, see Step 15. Using TCP/IP for communication.
- In
the controller initialization parameters:
- 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. - In the
ROUTOPTS
statement, write the TCP/IP destination name and IP address of the remote tracker in the TCPIP keyword.
- In the
- 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. - In
the tracker initialization parameters:
- In the
TCPOPTS
statement, set the values to define the details of the local tracker or leave the default values. - In
the
TRROPTS
statement, set theHOSTCON()
keyword toTCPIP
and write the IP address of the controller in theTCPHOSTNAME()
keyword. - In
the
EWTROPTS
statement, set theEWSEQNO()
keyword to 1.
- In the
- Stop and restart the controller and tracker for the parmlib changes
to take effect, and run the
CP extend
or theCP replan
command to update the current plan with the changed workstation destinations.