Determining Scheduling Characteristics

One of the main purposes of a TP profile is to describe the environment necessary to schedule and run the TP. This information usually comes from the scheduling section of the profile. When scheduling information is missing from a TP profile and the TP is scheduled with the APPC/MVS transaction scheduler, the OPTIONS and TPDEFAULT statements in an ASCHPMxx parmlib member can provide some defaults, such as a scheduling class. However, for proper scheduling of TPs running under the APPC/MVS transaction scheduler, give consideration to each parameter in the scheduling section of the profile. Each of these parameters is explained in detail in Transaction Scheduler Section.

Transaction programs on MVS can be scheduled by the APPC/MVS transaction scheduler (ASCH) or by an installation-defined scheduler. How you define the scheduling portion of a TP profile depends on the transaction scheduler used. Before you create profiles, ask the person who determines scheduling policy for the following information:

For TPs scheduled by the APPC/MVS transaction scheduler:
- The class name to use for each type of TP. (For example, IBM® recommends that TPs scheduled as standard use a different class from those scheduled as multi-trans.)
- Whether a default has been established for class in an OPTIONS statement of ASCHPMxx.
- Whether default information was established in a TPDEFAULT statement of ASCHPMxx.
For TPs scheduled by a scheduler other than the APPC/MVS transaction scheduler:
- How the TP profile should be adapted to reflect scheduling characteristics of the transaction scheduler.
- The name of the transaction scheduler exit used to syntax check the TP profile information.