Values on the Add Standard Template window

Template source file
Optional file that describes the template and provides a shortcut for supplying values for other fields on the window. Specify the absolute z/OS® UNIX path of the file, beginning with the forward slash (/) and including the file name, for example, /u/jsmith/loadmeup.prop, or the name of a partitioned or sequential data set. Then, click Load to supply values for other fields on the window.
The file must be in Java™ property file format:
  • Each entry is a single line, in property=value or property:value format.
  • The \ character is a continuation character, so that a value can span lines.
  • For newline, carriage return, and tab, use \n, \r, and \t.
  • Comment characters are ! and #. Lines that start with those characters are ignored.
Example:
workflow-definition-file:/u/jsmith/workflow_definition.xml
workflow-variable-input-file:/u/jsmith/var_input_file
action-definition-file:/u/jsmith/actions_definition.xml
admin-documentation-file:/u/jsmith/documentation.txt
consumer-documentation-file:/u/jsmith/documentation.txt
Note: All relative paths that are specified in the manifest file are treated as being relative to the manifest file location.
Target domain
Name of the domain to associate with the template. Select a domain name from the list or accept the default domain. A domain name is required. Domains are defined with the Resource Management task.
Template name
Name of the template. A template name is required.
The name must be unique. It can include alphanumeric characters, or these special characters:
  • $
  • @
  • _
  • -
It can be up to 48 characters long.
Workflow file
Path for the workflow definition file. Specify the absolute z/OS UNIX path of the file, beginning with the forward slash (/) and including the file name, for example, /usr/lpp/zosmf/V2R2/workflows/workflow_sample.xml, or the name of a partitioned or sequential data set. A workflow file is required.
Actions file
Path for the actions definition file for use with the worfklow. This file describes the actions that can be performed against the instance that is created from the template. Specify the absolute z/OS UNIX path of the file, beginning with the forward slash (/) and including the file name, for example, /usr/lpp/zosmf/V2R2/workflows/workflow_actions.xml, or the name of a partitioned or sequential data set. An actions file is required.

To create an actions definition file, click Create New. (The Actions file field must be blank.)

For more information, see Working with actions.

Workflow variables input file
Path for the variables input file to use with the workflow. Specify the absolute z/OS UNIX path of the file, beginning with the forward slash (/) and including the file name, for example, /usr/lpp/zosmf/V2R2/workflows/workflow_variables.xml, or the name of a partitioned or sequential data set.
Consumer documentation file
Path for the documentation file for consumers. Specify the absolute z/OS UNIX path of the file, beginning with the forward slash (/) and including the file name, or the name of a partitioned or sequential data set. Select the file type with the File Type field.
Administrator documentation file
Path for the documentation file for administrators. Specify the absolute z/OS UNIX path of the file, beginning with the forward slash (/) and including the file name, or the name of a partitioned or sequential data set. Select the file type with the File Type field.
Template approvers
List of the user IDs of the approvers for the template. Separate approvers with commas or blanks. These are approvers for the template (sometimes called general approvers) as opposed to approvers for a specific step or action. Approvers receive a z/OSMF notification.
Template description
Description of the template.
Workflows disposition
Select Delete successful workflows on completion to cause the workflow that is used to provision the software, and all action workflows, to be deleted automatically after they complete successfully. The default is to keep the workflows.

If you do not specify that workflows should be deleted automatically, you can manually delete them from the workflows table in the Workflows task.

For action workflows, this setting can be overridden in the actions definition file.

Jobs disposition
Select Delete jobs on completion to cause the jobs that are dynamically submitted to be deleted automatically after they complete. The default is to keep the jobs.

If you do not specify that the jobs should be deleted automatically, you can manually delete the jobs.