Note the following points as you create and work with custom job templates:
You do not run a job template. You run a job instance derived from a job template.
To access user-defined templates and the OpenEdge Management-supplied database maintenance templates, select Jobs from the menu bar. Review the contents of the Defined Jobs and Job Templates categories that appear in the list frame.
When you create a job template, you can define schedule information, but you cannot enable the schedule to run with the template. This schedule definition can be enabled once you create an instance from the template.
You can associate one or more command actions with job templates.
You cannot define specific database resources for a job template. The job template is an outline of common values that you can copy and apply to various instances derived from the template. You associate specific database resources when you create a job instance.
Once you have created a job instance from a job template, these items are completely separate from each other. Edits to the job instance do not affect the job template, and edits to the job template do not affect instances previously derived from the template.
Unlike job instances, which can only be used local to the machine on which they are created, job templates can be exported and imported. However, the definition of job templates that you export or import does not include resource- or device-specific properties.
You do not run a job template. You run a job instance derived from a job template.