Chapter 3-1: Overview of APPX Processes Cover Page 3-01:Images3-01:Automatic and Optional Child Invocations

Process Control Files


A process can operate on the data that is contained in any number of files, but it can automatically manage a maximum of one file. This automatically managed file is referred to as the process control file (PCF). The PCF identifies the one file for which records are automatically read, written, rewritten, and deleted when the process executes. For example, the PCF for a customer maintenance input process is the customer file.

If you find it necessary to automatically maintain more than one file, such as updating sales order header information and line item information together, create a separate process for each file. You invoke the line item process as an automatic child from the sales order header process. Refer to the following sections, Automatic and Optional Child Invocation and Process Lineage, for additional information on parent and child processes.

A PCF is optional for input and output processes. An input process that does not include a PCF will execute once, and then automatically end (as opposed to executing once for every record). Output processes that do not specify a PCF can be used, for example, to produce standardized page headings and page footers.

Query, update, and inquiry processes must have a process control file. Menu, job, status, and subroutine processes cannot have a PCF.

 

APPX Application Design Manual (01/13/03) Cover Page 3-01:Images3-01:Automatic and Optional Child Invocations

© 2003 by APPX Software, Inc. All rights reserved