Scheduler Specification Flexibility

Keep the following in mind when setting up your system. See the ChangeMan ZMF ERO Getting Started Guide and ChangeMan ZMF XML Services User’s guide for more details on Scheduler interaction.

There are three global admin scheduler types: CMN, Manual and other. This defines which of the 3 scheduler types to enable in application and release admin, and the default scheduler to use when defining new applications and releases.

Equivalent scheduler parameters are available in application admin. This defines which scheduler types may be selected when creating or updating a package and which scheduler type is set by default when creating a package.

Equivalent scheduler parameters are also available to the ERO functions that create and update a release. This defines which scheduler types may be selected when creating or updating a package attached to the release and which scheduler type is set by default when creating a package attached to the release.

A new package attached to a release will default to the release default scheduler, not the application default scheduler.

A new package created using the short and copy forward method will use the application or release default scheduler, not the scheduler from the package used as a model. The scheduler from the model package may not be valid, will not be displayed and can not be changed using the short method.

A new package created in ZMF/ISPF using the long and copy, forward method will use the scheduler from the package used as a model. The scheduler from the model package may not be valid but can be changed using the long method.

A new package created using the package.service.create service using the copy forward method will use the scheduler from the package used as a model. If specified, the scheduler specified in the service request will be used instead. The scheduler from the model package may not be valid but can be changed by specifying a scheduler in the service request. This is similar to the ZMF/ISPF function using long and copy forward methods.

The scheduler for packages attached to a release must comply with both the application and release allowed schedulers.

The global and application parameter update services (parms.gbl.update, parms.appl.update/create) perform minimal validation. These services do not ensure consistency between different global parameters or between different application parameters. The application update service does ensure that application updates conform to global restriction rules. The application update service will prevent setting a scheduler to be allowed if it is not allowed in global parameters. It will prevent setting a default scheduler other than '1', '2' or '3' (cmn, manual or other). The global and application update services ignore allowed scheduler values other than 'Y' and 'N'. These services allow setting a default scheduler that is not an allowed scheduler.

The release configuration service (rlsmrlse.service.config) will prevent setting a scheduler to be allowed if it is not allowed in global parameters. It will prevent setting a default scheduler that is not allowed in global parameters. It will prevent setting a default scheduler that is being disallowed in the current service call.

See the ChangeMan ZMF ERO Getting Started Guide and ChangeMan ZMF XML Services User’s Guide for more details on how the Scheduler interacts with these facilities.