Checking for scheduling environment availability

The tracker submitting the job uses the WLM Query Service to check if the scheduling environment is available:
  • If the scheduling environment is available on any system in the sysplex, the job is submitted and WLM has the task to identify the system where the job will run.

    Whenever the new OPCOPTS JESPLEX parameter is specified, the associated list of system names is used as an additional filter in the WLM query to check for scheduling environment availability at JESplex level. This is required when there are more than one JESplex within the same sysplex.

    Note: If you use virtual workstations with the WLM SCHENV interface, all the virtual destinations must be in the same sysplex and JESplex.

    Based on WLM logic, to obtain full workload balancing, you should configure no more than one JESplex in the sysplex. However, deviations from this rule are often found throughout the installed basis. For a description of the new parameter and a troubleshooting for configuration problems, refer to Multi-sysplex configuration with JESplex matching sysplex.

  • If the scheduling environment is not available on any system in the sysplex (or at the tracker JESplex level if the OPCOPTS JESPLEX parameter is specified) the operation is assigned the Ready status and the Waiting for scheduling environment extended status.

    This process is not followed if the operation comes from the Restart and Clean up path. In this case, the operation is assigned the SERC (SE not available for R&C operation) error status. Operations that are ready but waiting for the scheduling environment to be available are considered not eligible for submission by the controller.

  • If the scheduling environment is not defined in the sysplex, the operation status is set to Error with the SEUN (SE undefined) error code.