The following table describes parameters for a Sub Folder that is used to define scheduling, prerequisites, and actions of the jobs contained in the Sub Folder. Only Control-M/Server for Distributed Systems supports Sub Folders in SMART Folders.
| Parameter | Description | 
|---|---|
| Indicates whether the folder type is a regular folder, a SMART folder, or a Sub Folder. | |
| Defines the name of the folder. In the Properties pane, this parameter indicates the folder where the job belongs. | |
| Provides a description of the job in free text. A well written description can help you determine why the job was defined and how it fits into your business workflow. | |
| Reference | Defines the sub-folder as a Reference sub-folder. A Reference sub-folder references to a SMART folder or a job within a SMART folder. The following sub-folder properties are updated with values from the referenced SMART folder or job, if these properties are not set: 
 | 
| Reference Path | Defines the full reference path name, such as referenceFolder2/job7. Valid values: 
 
 | 
| Defines the name of the Control-M/Server (or Control-M for z/OS) that processes the job. | |
| Identifies the user name with the authorization to execute the job. This parameter is used by the Control-M security mechanism. | |
| Parent Folder | Defines the name of the folder that contains the job or Sub Folder. Names of folders and Sub Folders may be up to 64 characters, with the exception of Control-M for z/OS folders which may be up to 8 characters. Folder names cannot contain the character “/”. SMART Folders in Control-M for z/OS can only contain jobs (not Sub Folders). | 
| More | Defines an area of the Properties pane to click to define more parameters. | 
| All variables are identified by the %% prefix. If %% is included in the value for a job processing parameter, Control‑M assumes that it is referring to a variable or function. You can add a variable, as described in Adding a variable. | |
| Provides a logical name for sorting groups of jobs. This parameter is used to supply a common descriptive name to a set of related job groups. The jobs do not necessarily have to run at the same time. | |
| Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application parameter. For example, the Application is Finances, and the Sub Application is Payroll. | |
| Indicates the Control‑M/EM user who defined the job. | |
| Documentation | Defines a description related to the job, and is saved in a defined location. The Documentation area in the Properties pane includes information about where to find the Documentation. In a z/OS job, the Documentation is in a Doc Member located in a Doc Library. In a non-z/OS job, the Documentation depends on whether the type is File or URL. For a file, the description is located in a file located in a file path. For a URL, the Documentation is located in a URL address. | 
| Defines whether the documentation for an OS job is in a file or URL. See the following: 
 | |
| For a z/OS job, Doc Library defines the name of the library where the Documentation (description) is saved. For a non-z/OS job, Doc Path defines the name of the file path where the Documentation is saved. | |
| For a z/OS job, defines the name of the member where the job Documentation (description) is saved. For a non-z/OS job, the Doc File is the name of the file where the job Documentation is saved. | |
| Determines the order of job processing by Control-M in the Active Jobs database. | 
| Parent Topic |