Submitting prevention and automatic tailoring

If a scheduling environment is associated to an operation, when the time to submit the operation arrives:
  • The scheduling environment is monitored for availability at tracker level. The tracker does not submit the operation as long as the scheduling environment is not available.
  • The JCL is tailored by inserting the SCHENV=CP defined Scheduling Environment name parameter in the JCL JOB card if the availability check is positive.
Scheduling environments are monitored and defined in the JCLs according to the value of the OPCOPTS SECHECK parameter specified in the tracker that will be submitting the operation. You have the option to:
  • Not use scheduling environments (no check nor tailoring).
  • Manage scheduling environments only if they are defined at operation level in the current plan.
  • Manage scheduling environments also if the related operations do not have the association defined in the current plan but have the JCL containing the SCHENV= keyword.

For details, see Customization and Tuning.