Setting Section Properties
Controls that specify section properties are located in the Definition view. For example, for each section included in your program, a node, as shown in the following example, appears. You specify all of the attributes to associate with a particular section from this node:
This example illustrates the fields and controls on the Section object. You can find definitions for the fields and controls later on this page.

The values you specify at the section level generally apply to all the objects contained within that section.
| Field or Control | Description |
|---|---|
|
Section Name |
Develop a naming convention and use it consistently throughout your projects. You are limited to eight characters. |
|
Market |
Select the market for which the section is intended. If a particular market is irrelevant to your batch program, keep the default market value of Global (GBL). |
|
Platform |
Select the target database platform for which this section definition will run. Leave the default value for all sections whose defined actions are not specific to a given database platform. |
|
Effective Date |
To make a particular section effective-dated, enter a target date. |
|
Effective Status |
Specify whether a section is active or enabled at runtime. |
|
Section Type |
If the program terminates abnormally, this value specifies whether you must restart the section. If a section controls a procedure that, if not run to completion, could corrupt or desynchronize your data, then select Critical Updates. Otherwise, accept the default value of Prepare Only. |
|
Auto Commit |
Select to specify the commit level for the section. You can have no commit or you can have Application Engine commit after the step successfully completes. |
|
Public |
Select to enable a section to be called from another program. |