Dialog response

This section helps you to understand the factors that affect the performance of the general service subtask and identifies actions to address those factors.

Factors that influence response times

Consider these factors:

• The number of operations in the plan and the size of the networks. The current plan consists of networks of occurrences. Occurrences with dependent operations are inserted on the same network. In many installations, the size of the largest network can be as much as 80% of the entire plan. When a modify request is processed by the general service task, for example, to add an occurrence with dependencies, IBM Tivoli Workload Scheduler for z/OS must ensure that the change does not cause a loop in the network.
• Specific request types that initiate network scans. For example, modifying a dependency in the MCP dialog.
• Poor construction of list requests resulting in sequential searches of the current plan data set.
• Time taken to search the ISPxLIB concatenation for panels, messages, load modules.

Recommendations

Consider these recommendations:

• Use GSTASK(5), the maximum value to increase parallelism for dialog requests.
• Use FASTPATH=Y for job name table searches on panels 6.3 and 5.3.
• Choose to traverse the network for dependency loops only when the change is stored, rather than on the panel where you define the dependency and also when the change is stored, When external dependencies are modified in the current plan. Use DEP CHECK=N in the MCP dependency panels to remove the network scan on that panel.
• Consider using LIBDEFs for the ISPF allocations if there are many libraries already concatenated on ISPxLIB.
• Consider moving EQQMINOJ, EQQXDSPX and EQQXTBLX into an LPA library. These modules are loaded by dialog users every time they enter an option from the IBM Tivoli Workload Scheduler for z/OS main menu.
• Determine when to use and when not to use generics, avoid using generic characters in the first position of a field. Study the key structure of the current plan records.
• Eliminate much of the active monitoring of operations in the current plan by using the automatic alert functions provided by IBM Tivoli Workload Scheduler for z/OS.