Sections

Control	Description
Section Name	Be as descriptive as possible – 8 character limit
Description	Descriptive name for the Section – 30 character limit
Market	The market for which the Section is intended. If a particular market is irrelevant to your batch program, leave as GBL
Platform	Used to specify Section is to be run on a particular platform. Enables you to take advantage of any RDBMS-specific optimizations or to change section logic because of RDBMS limitations.
Effective Date	Default is 01/01/1900. May be used to make a particular Section effective-dated
Effective Status	Used to activate/inactivate a Section
Section Type	In case of abend, the value of this system field specifies whether or not the Section will need to be restarted. If a section controls a procedure that, if not run to completion, could corrupt or desynchronize your data, select Critical Updates. Otherwise, use the default value of Preparation Only.
Auto Commit	Specify the COMMIT level for the section. Can opt to have not COMMIT or have AppEngine COMMIT after each Step in the Section successfully completes (not efficient!)
Access	This property controls the Call Section Action. Specify that a Section can or can’t be called from another program
Comments	Use the comments section to document the Section

Steps

Control	Description
Step Name	Consecutively numbered based on the last step name – 8 char limit
Step Description	Descriptive name for the Step – 30 character limit
Commit After	Determines when COMMIT will be executed: - Default: uses values supplied for the Section - Later: do not COMMIT now - After Step: COMMIT when step completes Note: “Later” and “After Step” override the Section “Auto Commit” setting
Frequency	Only available in loops
On Error	Determines the action to take when an error occurs: - Abort: program will write messages to message log and terminate - Ignore: program will write messages to message log and continue - Suppress: no message will be written, but program will continue
Active	Determines if the Step is active (checked) or inactive (blank)
Comments	Add any additional comments to document the program

Action Execution Order


1. Do When

2. Do While

3. Do Select

4. PeopleCode

5. SQL or Call Section

6. Message Log

7. Do Until

8. XSLT (enabled for transformation programs in rel 8.4)

Notes: SQL and Call Section are mutually exclusive


XSLT not available in LS

Do When, Do While, Do Until (iterative) Action Properties

    ReUse Statement is an option that can be enabled to optimize the SQL components of a batch program. Selecting this means the database engine only needs to compile the SQL once, this reduces SQL overhead. Choices are Yes, No, and Bulk Insert.


Do Select (iterative) Action Properties

    ReUse Statement: (See Do When, Do While, and Do Until above)

   Do Select Type: You need to specify one of the following: Select/Fetch, Reselect, or Restartable.

PeopleCode Action Properties

    On Return: If your PeopleCode program provides a false result, you can have Application Engine respond by doing one of the following: Abort, Break, or Skip Step.

SQL Action Properties

    ReUse Statement: (See Do When, Do While, and Do Until above)

    No Rows: If your SQL statement doesn't affect any rows, you can specify that Application Engine respond in one of the following ways: Abort, Section Break, Continue, or Skip Step.
            Abort: the program terminates
            Section Break: AppEngine exits the current Section immediately and control returns to the calling Step
           Continue: the program continues processing
           Step: AppEngine exits the current Step immediately and moves on to the next Step. When using Skip Step, keep the following in mind:
                         AppEngine ignores the commit for the current Step at runtime
                         If the current Step contains only one Action, only use Skip Step to bypass the commit
Call Section Action Properties

    Section Name: If you are calling another Section, you need to specify the appropriate Section here. Only the names of Public Sections defined in the program identified in Program ID will appear in the Section Name drop-down list.

    Program ID: Since you can call Sections in the current program or Sections that exist within other programs, you need to specify the Program ID, or Program Name, of the program containing the Section you intend to call. The drop-down list contains all of the program definitions that currently exist.


Log Message Action Properties

    Message Set: Identifies a message set within the Message Catalog.

    Number: Identifies a particular message within a Message Set.

    Parameters: A list of comma-delimited values to substitute for %1, %2, and so on markers in the message text.