Defining destinations with the ROUTOPTS statement

HCL Workload Automation Agents and dynamic domain managers are connected to the Z controller. This means that you use the ROUTOPTS statement to define the connection details of an HCL Workload Automation Agent and dynamic domain manager to the controller or standby controller.

Set the HTTP or HTTPS keyword to define all your HCL Workload Automation Agent destinations. For HCL Workload Automation Agents and dynamic domain managers, a destination is the combination of a name and the fully qualified host name, or IP address, and port number of the HCL Workload Automation Agent or dynamic domain manager.

HTTP and HTTPS have the same syntax. The difference is that HTTPS defines the connection as SSL-secure. ROUTOPTS is defined in the member of the EQQPARM library specified by the PARM parameter in the JCL EXEC statement of the controller.

The syntax for defining HCL Workload Automation Agent and dynamic domain managers destinations is the following:

ROUTOPTS HTTP|HTTPS(destination,...,destination)

where destination is indicated as follows:

For HCL Workload Automation Agents

dest name:'hostname or IPaddr of agent'/port of agent[/type][/pulseivl][/proxyname]

For more information, see Static end-to-end environment with Java run time installed in which you can run job types with advanced options.

For dynamic domain managers

hostname or IPaddress of DDM/port of DDM/B[/pulseivl]

For more information, see Dynamic end-to-end environment to run also job types with advanced options..

For master domain managers

hostname or IPaddress of MDM/port of MDM/B

The destination name is any alphanumeric sequence of up to 8 characters. You can include as many destinations as you want within the parentheses. They must be separated by commas. Because you cannot specify more than 455 lines for each ROUTOPTS statement, you can add further destinations by specifying more than one ROUTOPTS statement.

The pulseivl value is optional and defines the frequency, expressed in minutes, with which the HCL Workload Automation for Z controller checks that the agent or dynamic domain manager is running. Values range from 0 to 1440 minutes; the value 0 means that the heartbeat checking:

Is not run for z-centric agents.
Is run for dynamic domain managers according to the policy established by the Z controller.

For details, see Configuring the heartbeat checking interval for z-centric agents and dynamic domain managers.

Note: Any pulseivl value defined in a ROUTOPTS HTTP|HTTPS destination statement overrides the global value eventually defined with the HTTPOPTS PULSEIVL keyword.

The following example specifies the destinations to two HCL Workload Automation Agents:

ROUTOPTS HTTPS(ITAAC1:'192.27.144.12'/44112, ITAAC2:'192.14.55.231'/61424//10)

where a heartbeat checking interval of 10 minutes is set for ITAAC2. Note that if you use pulseivl, there must be two slashes (/) before it because the type parameter for z-centric agents is null.

The following example specifies the destination to one dynamic domain manager:

ROUTOPTS HTTPS(BRKS:'9.168.125.59'/8081/B/5)

where a heartbeat checking interval of 5 minutes is set for the dynamic domain manager.

The proxyname value is optional: you specify it when one or more z-centric agents are connected to the controller through a proxy server. You must have defined the proxyname in the PROXY parameter of ROUTOPTS.

The following example defines that the z-centric agents ZCENT1 and ZCENT2 are connected to the controller through the proxy server named PRX1 (you defined PRX1 in the PROXY parameter of ROUTOPTS):

ROUTOPTS HTTPS(ZCENT1:'192.27.144.12'/8081///PRX1, ZCENT2:'192.14.55.231'/16789//5/PRX1)
         PROXY(PRX1:'195.34.134.10'/3741)

You can modify, add, or delete an HTTP or HTTPS destination while HCL Workload Automation for Z is running. To make the changes immediately effective, without stopping and restarting the controller, issue the MODIFY command /F procname,RFRDEST.

Note: The RFRDEST command does not update any changes you make to the PROXY parameter in ROUTOPTS, it updates only the HTTP | HTTPS destinations, including the proxy name. For detailed information about RFRDEST, see Managing the Workload.

To list the HTTP and HTTPS destinations that are currently used by the controller, enter the following MODIFY command (the list is stored in the MLOG):

/F procname,DSPDEST

For detailed information about the DSPDEST command, see Managing the Workload.

You can add a maximum of 100 destinations, without having to restart the controller. The MODIFY command manages up to a total of 100 new destinations, regardless if you add them at once or at different times. After 100 destinations added, you must stop and restart the controller to have the MODIFY command manage other 100 new destinations.

Note: Deleting a destination does not increment the number of maximum additions allowed.

You can modify or delete an unlimited number of destinations. However, if you modify the destination name this operation is considered as adding a new destination.