User actions to activate scheduling environment integration

About this task

Following is a list of the required steps to activate scheduling environment integration.
Note: If you do not want to activate scheduling environment integration, no specific actions are requested. By default, the initialization parameters are set for no integration.
  1. To activate the function, for each tracker (and for the controller if it uses the submit function) set the SECHECK parameter to a value other than NO. Depending on your requirements, set to ALL or to OPERONLY:
    ALL
    If you do not plan to define the scheduling environment in the HCL Workload Automation for Z database
    OPERONLY
    All the other cases.
  2. If you use a multi-sysplex configuration, define the new OPCOPTS SYSPLEXID parameter for each tracker. This must be a unique number throughout the entire configuration.
  3. If you use multiple JESplex within a sysplex, define the new OPCOPTS JESPLEX parameter for each tracker. This must be a list of system names belonging to the tracker JESplex.or use scheduling environment best practice definitions.
Following is a list of the optional steps to activate scheduling environment integration:
  1. Define a scheduling environment at operation level.
  2. Implement the EQQUX001 controller exit routine to set the scheduling environment name if appropriate.
  3. Implement the EQQDPX01 exit routine to set the scheduling environment name if appropriate (for details, see Performance considerations).
  4. Set the SUPPRESSENF parameter to YES, where applicable, to improve performance (for details, see Performance considerations).